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] argh. i deleted the internal partitions, no boot, no download mode

I have, or perhaps it is now had, a P3113 - and in a moment of what would later be clear as stupidity, I wiped all the internal partitions. I went through and deleted them and then created some new ones - using parted. Evidence of the stupidity is below.
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
Model: MMC M8G2FB (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
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 27.3MB 2097kB SBL1
3 27.3MB 29.4MB 2097kB 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 789MB 734MB ext4 CACHE
8 789MB 810MB 21.0MB MODEM
9 810MB 2278MB 1468MB ext4 FACTORYFS
10 2278MB 7281MB 5004MB ext4 DATAFS
11 7281MB 7818MB 537MB ext4 HIDDEN
(parted) rm 1
rm 1
(parted) print
print
Model: MMC M8G2FB (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
2 25.2MB 27.3MB 2097kB SBL1
3 27.3MB 29.4MB 2097kB 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 789MB 734MB ext4 CACHE
8 789MB 810MB 21.0MB MODEM
9 810MB 2278MB 1468MB ext4 FACTORYFS
10 2278MB 7281MB 5004MB ext4 DATAFS
11 7281MB 7818MB 537MB ext4 HIDDEN
(parted) rm 2
rm 2
(parted) rm 3
rm 3
(parted) rm 4
rm 4
(parted) rm 5
rm 5
(parted) rm 6
rm 6
(parted) rm 7
rm 7
Error: Partition /dev/block/mmcblk0p7 is being used. You must unmount it before
you modify it with Parted.
(parted) rm 8
rm 8
(parted) 9
rm 9
(parted) 10
rm 10
(parted) 11
rm 11
(parted) print
print
Model: MMC M8G2FB (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
7 54.5MB 789MB 734MB ext4 CACHE
(parted) rm 7
rm 7
Error: Partition /dev/block/mmcblk0p7 is being used. You must unmount it before
you modify it with Parted.
(parted) >
>
check NUMBER do a simple check on the file system
cp [FROM-DEVICE] FROM-NUMBER TO-NUMBER copy file system to another partition
help [COMMAND] print general help, or help on
COMMAND
mklabel,mktable LABEL-TYPE create a new disklabel (partition
table)
mkfs NUMBER FS-TYPE make a FS-TYPE file system on
partititon NUMBER
mkpart PART-TYPE [FS-TYPE] START END make a partition
mkpartfs PART-TYPE FS-TYPE START END make a partition with a file system
move NUMBER START END move partition NUMBER
name NUMBER NAME name partition NUMBER as NAME
print [devices|free|list,all|NUMBER] display the partition table,
available devices, free space, all found partitions, or a particular
partition
quit exit program
rescue START END rescue a lost partition near START
and END
resize NUMBER START END resize partition NUMBER and its file
system
rm NUMBER delete partition NUMBER
select DEVICE choose the device to edit
set NUMBER FLAG STATE change the FLAG on partition NUMBER
toggle [NUMBER [FLAG]] toggle the state of FLAG on partition
NUMBER
unit UNIT set the default unit to UNIT
version display the version number and
copyright information of GNU Parted
(parted) rm 7
rm 7
(parted) print
print
Model: MMC M8G2FB (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
(parted) ^C
(parted)
Information: You may need to update /etc/fstab.
~ # parted /dev/block/mmcblk
mmcblk0 mmcblk0boot1 mmcblk0p11 mmcblk1 mmcblk1p2
mmcblk0boot0 mmcblk0p10 mmcblk0p9 mmcblk1p1
~ # parted /dev/block/mmcblk
mmcblk0 mmcblk0boot1 mmcblk0p11 mmcblk1 mmcblk1p2
mmcblk0boot0 mmcblk0p10 mmcblk0p9 mmcblk1p1
~ # parted /dev/block/mmcblk
mmcblk0 mmcblk0boot1 mmcblk0p11 mmcblk1 mmcblk1p2
mmcblk0boot0 mmcblk0p10 mmcblk0p9 mmcblk1p1
~ # parted /dev/block/mmcblk1
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk1
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
Model: SD SD (sd/mmc)
Disk /dev/block/mmcblk1: 32.1GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 4194kB 20.8GB 20.8GB primary fat32 lba
2 20.8GB 32.1GB 11.3GB primary ext3
(parted) rm 1
rm 1
(parted) rm 2
rm 2
(parted) ^C
(parted)
Information: You may need to update /etc/fstab.
~ # parted /dev/block/
loop0 loop7 mmcblk0p9 ram12 ram5
loop1 mmcblk0 mmcblk1 ram13 ram6
loop2 mmcblk0boot0 platform/ ram14 ram7
loop3 mmcblk0boot1 ram0 ram15 ram8
loop4 mmcblk0p10 ram1 ram2 ram9
loop5 mmcblk0p11 ram10 ram3
loop6 mmcblk0p7 ram11 ram4
~ # parted /dev/block/
loop0 loop7 mmcblk0p9 ram12 ram5
loop1 mmcblk0 mmcblk1 ram13 ram6
loop2 mmcblk0boot0 platform/ ram14 ram7
loop3 mmcblk0boot1 ram0 ram15 ram8
loop4 mmcblk0p10 ram1 ram2 ram9
loop5 mmcblk0p11 ram10 ram3
loop6 mmcblk0p7 ram11 ram4
~ # parted /dev/block/mmcblk
mmcblk0 mmcblk0boot1 mmcblk0p11 mmcblk0p9
mmcblk0boot0 mmcblk0p10 mmcblk0p7 mmcblk1
~ # parted /dev/block/mmcblk
mmcblk0 mmcblk0boot1 mmcblk0p11 mmcblk0p9
mmcblk0boot0 mmcblk0p10 mmcblk0p7 mmcblk1
~ # 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
Model: MMC M8G2FB (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
(parted) mkpartfs primary fat32 0 7000
mkpartfs primary fat32 0 7000
Error: Error informing the kernel about modifications to partition
/dev/block/mmcblk0p1 -- Device or resource busy. This means Linux won't know
about any changes you made to /dev/block/mmcblk0p1 until you reboot -- so you
shouldn't mount it or use it in any way before rebooting.
Ignore/Cancel? i
i
(parted) mkpartfs primary ext2 7000 7400
mkpartfs primary ext2 7000 7400
Error: Error informing the kernel about modifications to partition
/dev/block/mmcblk0p1 -- Device or resource busy. This means Linux won't know
about any changes you made to /dev/block/mmcblk0p1 until you reboot -- so you
shouldn't mount it or use it in any way before rebooting.
Ignore/Cancel? i
i
Error: Error informing the kernel about modifications to partition
/dev/block/mmcblk0p2 -- Device or resource busy. This means Linux won't know
about any changes you made to /dev/block/mmcblk0p2 until you reboot -- so you
shouldn't mount it or use it in any way before rebooting.
Ignore/Cancel? i
i
(parted) mkpartfs primary linux-swap 7400 7818
mkpartfs primary linux-swap 7400 7818
Error: Error informing the kernel about modifications to partition
/dev/block/mmcblk0p1 -- Device or resource busy. This means Linux won't know
about any changes you made to /dev/block/mmcblk0p1 until you reboot -- so you
shouldn't mount it or use it in any way before rebooting.
Ignore/Cancel? i
i
Error: Error informing the kernel about modifications to partition
/dev/block/mmcblk0p2 -- Device or resource busy. This means Linux won't know
about any changes you made to /dev/block/mmcblk0p2 until you reboot -- so you
shouldn't mount it or use it in any way before rebooting.
Ignore/Cancel? i
i
Error: Error informing the kernel about modifications to partition
/dev/block/mmcblk0p3 -- Device or resource busy. This means Linux won't know
about any changes you made to /dev/block/mmcblk0p3 until you reboot -- so you
shouldn't mount it or use it in any way before rebooting.
Ignore/Cancel? i
i
(parted) quit
quit
Information: You may need to update /etc/fstab.
~ # upgrade_fs
/sbin/sh: upgrade_fs: not found
~ #
~ # print
/sbin/sh: print: not found
~ # 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
Model: MMC M8G2FB (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 17.4kB 7000MB 7000MB fat32 msftres
2 7000MB 7400MB 400MB ext2
3 7400MB 7818MB 418MB linux-swap(v1)
(parted)
~ # ls
boot etc sd-ext
cache init sdcard
charger init.rc sys
data misc system
datadata proc tmp
default.prop res ueventd.espresso.rc
dev root ueventd.goldfish.rc
emmc sbin ueventd.rc
~ # ls /
boot etc sd-ext
cache init sdcard
charger init.rc sys
data misc system
datadata proc tmp
default.prop res ueventd.espresso.rc
dev root ueventd.goldfish.rc
emmc sbin ueventd.rc
~ # ls /boot/
~ # du -hs
So, now my internal SD card has (or I think it has) a partition that looks like this
Code:
1 17.4kB 7000MB 7000MB fat32 msftres
2 7000MB 7400MB 400MB ext2
3 7400MB 7818MB 418MB linux-swap(v1)
This clearly didn't sit well with it. It no longer boots, no screen, no nothing. No download mode. When I plug it into the computer and start it, I get a brief moment where it starts to act like a USB device, then disappears, then restarts. ADB can't see it.
I'm pretty sure I'm screwed here. I've tried Odin and Heimdall, on ubuntu, XP, win7. None can reach the device.
Is there any chance I can get this to run by creating an external SD card with the correct partitions on it? I read a few posts where people were able to run a device that had a corrupt SD internal card on the external one.
Any help greatly appreciated.

really ?
atomatomatomatom said:
I have, or perhaps it is now had, a P3113 - and in a moment of what would later be clear as stupidity, I wiped all the internal partitions. I went through and deleted them and then created some new ones - using parted. Evidence of the stupidity is below.
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
Model: MMC M8G2FB (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
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 27.3MB 2097kB SBL1
3 27.3MB 29.4MB 2097kB 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 789MB 734MB ext4 CACHE
8 789MB 810MB 21.0MB MODEM
9 810MB 2278MB 1468MB ext4 FACTORYFS
10 2278MB 7281MB 5004MB ext4 DATAFS
11 7281MB 7818MB 537MB ext4 HIDDEN
(parted) rm 1
rm 1
(parted) print
print
Model: MMC M8G2FB (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
2 25.2MB 27.3MB 2097kB SBL1
3 27.3MB 29.4MB 2097kB 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 789MB 734MB ext4 CACHE
8 789MB 810MB 21.0MB MODEM
9 810MB 2278MB 1468MB ext4 FACTORYFS
10 2278MB 7281MB 5004MB ext4 DATAFS
11 7281MB 7818MB 537MB ext4 HIDDEN
(parted) rm 2
rm 2
(parted) rm 3
rm 3
(parted) rm 4
rm 4
(parted) rm 5
rm 5
(parted) rm 6
rm 6
(parted) rm 7
rm 7
Error: Partition /dev/block/mmcblk0p7 is being used. You must unmount it before
you modify it with Parted.
(parted) rm 8
rm 8
(parted) 9
rm 9
(parted) 10
rm 10
(parted) 11
rm 11
(parted) print
print
Model: MMC M8G2FB (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
7 54.5MB 789MB 734MB ext4 CACHE
(parted) rm 7
rm 7
Error: Partition /dev/block/mmcblk0p7 is being used. You must unmount it before
you modify it with Parted.
(parted) >
>
check NUMBER do a simple check on the file system
cp [FROM-DEVICE] FROM-NUMBER TO-NUMBER copy file system to another partition
help [COMMAND] print general help, or help on
COMMAND
mklabel,mktable LABEL-TYPE create a new disklabel (partition
table)
mkfs NUMBER FS-TYPE make a FS-TYPE file system on
partititon NUMBER
mkpart PART-TYPE [FS-TYPE] START END make a partition
mkpartfs PART-TYPE FS-TYPE START END make a partition with a file system
move NUMBER START END move partition NUMBER
name NUMBER NAME name partition NUMBER as NAME
print [devices|free|list,all|NUMBER] display the partition table,
available devices, free space, all found partitions, or a particular
partition
quit exit program
rescue START END rescue a lost partition near START
and END
resize NUMBER START END resize partition NUMBER and its file
system
rm NUMBER delete partition NUMBER
select DEVICE choose the device to edit
set NUMBER FLAG STATE change the FLAG on partition NUMBER
toggle [NUMBER [FLAG]] toggle the state of FLAG on partition
NUMBER
unit UNIT set the default unit to UNIT
version display the version number and
copyright information of GNU Parted
(parted) rm 7
rm 7
(parted) print
print
Model: MMC M8G2FB (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
(parted) ^C
(parted)
Information: You may need to update /etc/fstab.
~ # parted /dev/block/mmcblk
mmcblk0 mmcblk0boot1 mmcblk0p11 mmcblk1 mmcblk1p2
mmcblk0boot0 mmcblk0p10 mmcblk0p9 mmcblk1p1
~ # parted /dev/block/mmcblk
mmcblk0 mmcblk0boot1 mmcblk0p11 mmcblk1 mmcblk1p2
mmcblk0boot0 mmcblk0p10 mmcblk0p9 mmcblk1p1
~ # parted /dev/block/mmcblk
mmcblk0 mmcblk0boot1 mmcblk0p11 mmcblk1 mmcblk1p2
mmcblk0boot0 mmcblk0p10 mmcblk0p9 mmcblk1p1
~ # parted /dev/block/mmcblk1
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk1
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
Model: SD SD (sd/mmc)
Disk /dev/block/mmcblk1: 32.1GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 4194kB 20.8GB 20.8GB primary fat32 lba
2 20.8GB 32.1GB 11.3GB primary ext3
(parted) rm 1
rm 1
(parted) rm 2
rm 2
(parted) ^C
(parted)
Information: You may need to update /etc/fstab.
~ # parted /dev/block/
loop0 loop7 mmcblk0p9 ram12 ram5
loop1 mmcblk0 mmcblk1 ram13 ram6
loop2 mmcblk0boot0 platform/ ram14 ram7
loop3 mmcblk0boot1 ram0 ram15 ram8
loop4 mmcblk0p10 ram1 ram2 ram9
loop5 mmcblk0p11 ram10 ram3
loop6 mmcblk0p7 ram11 ram4
~ # parted /dev/block/
loop0 loop7 mmcblk0p9 ram12 ram5
loop1 mmcblk0 mmcblk1 ram13 ram6
loop2 mmcblk0boot0 platform/ ram14 ram7
loop3 mmcblk0boot1 ram0 ram15 ram8
loop4 mmcblk0p10 ram1 ram2 ram9
loop5 mmcblk0p11 ram10 ram3
loop6 mmcblk0p7 ram11 ram4
~ # parted /dev/block/mmcblk
mmcblk0 mmcblk0boot1 mmcblk0p11 mmcblk0p9
mmcblk0boot0 mmcblk0p10 mmcblk0p7 mmcblk1
~ # parted /dev/block/mmcblk
mmcblk0 mmcblk0boot1 mmcblk0p11 mmcblk0p9
mmcblk0boot0 mmcblk0p10 mmcblk0p7 mmcblk1
~ # 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
Model: MMC M8G2FB (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
(parted) mkpartfs primary fat32 0 7000
mkpartfs primary fat32 0 7000
Error: Error informing the kernel about modifications to partition
/dev/block/mmcblk0p1 -- Device or resource busy. This means Linux won't know
about any changes you made to /dev/block/mmcblk0p1 until you reboot -- so you
shouldn't mount it or use it in any way before rebooting.
Ignore/Cancel? i
i
(parted) mkpartfs primary ext2 7000 7400
mkpartfs primary ext2 7000 7400
Error: Error informing the kernel about modifications to partition
/dev/block/mmcblk0p1 -- Device or resource busy. This means Linux won't know
about any changes you made to /dev/block/mmcblk0p1 until you reboot -- so you
shouldn't mount it or use it in any way before rebooting.
Ignore/Cancel? i
i
Error: Error informing the kernel about modifications to partition
/dev/block/mmcblk0p2 -- Device or resource busy. This means Linux won't know
about any changes you made to /dev/block/mmcblk0p2 until you reboot -- so you
shouldn't mount it or use it in any way before rebooting.
Ignore/Cancel? i
i
(parted) mkpartfs primary linux-swap 7400 7818
mkpartfs primary linux-swap 7400 7818
Error: Error informing the kernel about modifications to partition
/dev/block/mmcblk0p1 -- Device or resource busy. This means Linux won't know
about any changes you made to /dev/block/mmcblk0p1 until you reboot -- so you
shouldn't mount it or use it in any way before rebooting.
Ignore/Cancel? i
i
Error: Error informing the kernel about modifications to partition
/dev/block/mmcblk0p2 -- Device or resource busy. This means Linux won't know
about any changes you made to /dev/block/mmcblk0p2 until you reboot -- so you
shouldn't mount it or use it in any way before rebooting.
Ignore/Cancel? i
i
Error: Error informing the kernel about modifications to partition
/dev/block/mmcblk0p3 -- Device or resource busy. This means Linux won't know
about any changes you made to /dev/block/mmcblk0p3 until you reboot -- so you
shouldn't mount it or use it in any way before rebooting.
Ignore/Cancel? i
i
(parted) quit
quit
Information: You may need to update /etc/fstab.
~ # upgrade_fs
/sbin/sh: upgrade_fs: not found
~ #
~ # print
/sbin/sh: print: not found
~ # 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
Model: MMC M8G2FB (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 17.4kB 7000MB 7000MB fat32 msftres
2 7000MB 7400MB 400MB ext2
3 7400MB 7818MB 418MB linux-swap(v1)
(parted)
~ # ls
boot etc sd-ext
cache init sdcard
charger init.rc sys
data misc system
datadata proc tmp
default.prop res ueventd.espresso.rc
dev root ueventd.goldfish.rc
emmc sbin ueventd.rc
~ # ls /
boot etc sd-ext
cache init sdcard
charger init.rc sys
data misc system
datadata proc tmp
default.prop res ueventd.espresso.rc
dev root ueventd.goldfish.rc
emmc sbin ueventd.rc
~ # ls /boot/
~ # du -hs
So, now my internal SD card has (or I think it has) a partition that looks like this
Code:
1 17.4kB 7000MB 7000MB fat32 msftres
2 7000MB 7400MB 400MB ext2
3 7400MB 7818MB 418MB linux-swap(v1)
This clearly didn't sit well with it. It no longer boots, no screen, no nothing. No download mode. When I plug it into the computer and start it, I get a brief moment where it starts to act like a USB device, then disappears, then restarts. ADB can't see it.
I'm pretty sure I'm screwed here. I've tried Odin and Heimdall, on ubuntu, XP, win7. None can reach the device.
Is there any chance I can get this to run by creating an external SD card with the correct partitions on it? I read a few posts where people were able to run a device that had a corrupt SD internal card on the external one.
Any help greatly appreciated.
Click to expand...
Click to collapse
it happens to me too as i tried to delete and create a new partition for swap. but i can go into the download mode and the recovery mode and it is really hard to get into the download and recovery mode.

Time for a new tab.
Or maybe you can use Hemidall /Linux ADB to setup original partitions.
Google is your friend.
Pp.

I googled a whole day away. No joy. My question is: is there any chance to recover this when there is no download mode? And as far as I can tell, there is no chance of adb or mounting that internal sdcard if the device won't go into download mode. Is that correct?
The only solution I saw, and this was on a different model, is to actually pry off the internal sdcard to force the device to boot off the external sdcard instead. I could then perhaps copy a working image onto the external sdcard on my computer using dd.
The other solution is perhaps a JTAG jig: http://forum.xda-developers.com/showpost.php?p=43555803&postcount=642 -but I am not sure if I've lobotomised my tablet past the point of ever entering download mode again.
I suspect what I have done is seriously confused it by changing the partition table. So, it is stuck in a loop, before it even gets to the download mode check.

Kowyim said:
it happens to me too as i tried to delete and create a new partition for swap. but i can go into the download mode and the recovery mode and it is really hard to get into the download and recovery mode.
Click to expand...
Click to collapse
Hard would be better than my current state of 'impossible' - how did you get it into download mode? I read that people hold it down for ages and it sometimes works. I suspect this may be a cruel joke - poor suckers sitting there holding their dead tablet for days on end.

atomatomatomatom said:
I have, or perhaps it is now had, a P3113 - and in a moment of what would later be clear as stupidity, I wiped all the internal partitions. I went through and deleted them and then created some new ones - using parted. Evidence of the stupidity is below.
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
Model: MMC M8G2FB (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
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 27.3MB 2097kB SBL1
3 27.3MB 29.4MB 2097kB 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 789MB 734MB ext4 CACHE
8 789MB 810MB 21.0MB MODEM
9 810MB 2278MB 1468MB ext4 FACTORYFS
10 2278MB 7281MB 5004MB ext4 DATAFS
11 7281MB 7818MB 537MB ext4 HIDDEN
(parted) rm 1
rm 1
(parted) print
print
Model: MMC M8G2FB (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
2 25.2MB 27.3MB 2097kB SBL1
3 27.3MB 29.4MB 2097kB 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 789MB 734MB ext4 CACHE
8 789MB 810MB 21.0MB MODEM
9 810MB 2278MB 1468MB ext4 FACTORYFS
10 2278MB 7281MB 5004MB ext4 DATAFS
11 7281MB 7818MB 537MB ext4 HIDDEN
(parted) rm 2
rm 2
(parted) rm 3
rm 3
(parted) rm 4
rm 4
(parted) rm 5
rm 5
(parted) rm 6
rm 6
(parted) rm 7
rm 7
Error: Partition /dev/block/mmcblk0p7 is being used. You must unmount it before
you modify it with Parted.
(parted) rm 8
rm 8
(parted) 9
rm 9
(parted) 10
rm 10
(parted) 11
rm 11
(parted) print
print
Model: MMC M8G2FB (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
7 54.5MB 789MB 734MB ext4 CACHE
(parted) rm 7
rm 7
Error: Partition /dev/block/mmcblk0p7 is being used. You must unmount it before
you modify it with Parted.
(parted) >
>
check NUMBER do a simple check on the file system
cp [FROM-DEVICE] FROM-NUMBER TO-NUMBER copy file system to another partition
help [COMMAND] print general help, or help on
COMMAND
mklabel,mktable LABEL-TYPE create a new disklabel (partition
table)
mkfs NUMBER FS-TYPE make a FS-TYPE file system on
partititon NUMBER
mkpart PART-TYPE [FS-TYPE] START END make a partition
mkpartfs PART-TYPE FS-TYPE START END make a partition with a file system
move NUMBER START END move partition NUMBER
name NUMBER NAME name partition NUMBER as NAME
print [devices|free|list,all|NUMBER] display the partition table,
available devices, free space, all found partitions, or a particular
partition
quit exit program
rescue START END rescue a lost partition near START
and END
resize NUMBER START END resize partition NUMBER and its file
system
rm NUMBER delete partition NUMBER
select DEVICE choose the device to edit
set NUMBER FLAG STATE change the FLAG on partition NUMBER
toggle [NUMBER [FLAG]] toggle the state of FLAG on partition
NUMBER
unit UNIT set the default unit to UNIT
version display the version number and
copyright information of GNU Parted
(parted) rm 7
rm 7
(parted) print
print
Model: MMC M8G2FB (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
(parted) ^C
(parted)
Information: You may need to update /etc/fstab.
~ # parted /dev/block/mmcblk
mmcblk0 mmcblk0boot1 mmcblk0p11 mmcblk1 mmcblk1p2
mmcblk0boot0 mmcblk0p10 mmcblk0p9 mmcblk1p1
~ # parted /dev/block/mmcblk
mmcblk0 mmcblk0boot1 mmcblk0p11 mmcblk1 mmcblk1p2
mmcblk0boot0 mmcblk0p10 mmcblk0p9 mmcblk1p1
~ # parted /dev/block/mmcblk
mmcblk0 mmcblk0boot1 mmcblk0p11 mmcblk1 mmcblk1p2
mmcblk0boot0 mmcblk0p10 mmcblk0p9 mmcblk1p1
~ # parted /dev/block/mmcblk1
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk1
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
Model: SD SD (sd/mmc)
Disk /dev/block/mmcblk1: 32.1GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 4194kB 20.8GB 20.8GB primary fat32 lba
2 20.8GB 32.1GB 11.3GB primary ext3
(parted) rm 1
rm 1
(parted) rm 2
rm 2
(parted) ^C
(parted)
Information: You may need to update /etc/fstab.
~ # parted /dev/block/
loop0 loop7 mmcblk0p9 ram12 ram5
loop1 mmcblk0 mmcblk1 ram13 ram6
loop2 mmcblk0boot0 platform/ ram14 ram7
loop3 mmcblk0boot1 ram0 ram15 ram8
loop4 mmcblk0p10 ram1 ram2 ram9
loop5 mmcblk0p11 ram10 ram3
loop6 mmcblk0p7 ram11 ram4
~ # parted /dev/block/
loop0 loop7 mmcblk0p9 ram12 ram5
loop1 mmcblk0 mmcblk1 ram13 ram6
loop2 mmcblk0boot0 platform/ ram14 ram7
loop3 mmcblk0boot1 ram0 ram15 ram8
loop4 mmcblk0p10 ram1 ram2 ram9
loop5 mmcblk0p11 ram10 ram3
loop6 mmcblk0p7 ram11 ram4
~ # parted /dev/block/mmcblk
mmcblk0 mmcblk0boot1 mmcblk0p11 mmcblk0p9
mmcblk0boot0 mmcblk0p10 mmcblk0p7 mmcblk1
~ # parted /dev/block/mmcblk
mmcblk0 mmcblk0boot1 mmcblk0p11 mmcblk0p9
mmcblk0boot0 mmcblk0p10 mmcblk0p7 mmcblk1
~ # 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
Model: MMC M8G2FB (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
(parted) mkpartfs primary fat32 0 7000
mkpartfs primary fat32 0 7000
Error: Error informing the kernel about modifications to partition
/dev/block/mmcblk0p1 -- Device or resource busy. This means Linux won't know
about any changes you made to /dev/block/mmcblk0p1 until you reboot -- so you
shouldn't mount it or use it in any way before rebooting.
Ignore/Cancel? i
i
(parted) mkpartfs primary ext2 7000 7400
mkpartfs primary ext2 7000 7400
Error: Error informing the kernel about modifications to partition
/dev/block/mmcblk0p1 -- Device or resource busy. This means Linux won't know
about any changes you made to /dev/block/mmcblk0p1 until you reboot -- so you
shouldn't mount it or use it in any way before rebooting.
Ignore/Cancel? i
i
Error: Error informing the kernel about modifications to partition
/dev/block/mmcblk0p2 -- Device or resource busy. This means Linux won't know
about any changes you made to /dev/block/mmcblk0p2 until you reboot -- so you
shouldn't mount it or use it in any way before rebooting.
Ignore/Cancel? i
i
(parted) mkpartfs primary linux-swap 7400 7818
mkpartfs primary linux-swap 7400 7818
Error: Error informing the kernel about modifications to partition
/dev/block/mmcblk0p1 -- Device or resource busy. This means Linux won't know
about any changes you made to /dev/block/mmcblk0p1 until you reboot -- so you
shouldn't mount it or use it in any way before rebooting.
Ignore/Cancel? i
i
Error: Error informing the kernel about modifications to partition
/dev/block/mmcblk0p2 -- Device or resource busy. This means Linux won't know
about any changes you made to /dev/block/mmcblk0p2 until you reboot -- so you
shouldn't mount it or use it in any way before rebooting.
Ignore/Cancel? i
i
Error: Error informing the kernel about modifications to partition
/dev/block/mmcblk0p3 -- Device or resource busy. This means Linux won't know
about any changes you made to /dev/block/mmcblk0p3 until you reboot -- so you
shouldn't mount it or use it in any way before rebooting.
Ignore/Cancel? i
i
(parted) quit
quit
Information: You may need to update /etc/fstab.
~ # upgrade_fs
/sbin/sh: upgrade_fs: not found
~ #
~ # print
/sbin/sh: print: not found
~ # 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
Model: MMC M8G2FB (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 17.4kB 7000MB 7000MB fat32 msftres
2 7000MB 7400MB 400MB ext2
3 7400MB 7818MB 418MB linux-swap(v1)
(parted)
~ # ls
boot etc sd-ext
cache init sdcard
charger init.rc sys
data misc system
datadata proc tmp
default.prop res ueventd.espresso.rc
dev root ueventd.goldfish.rc
emmc sbin ueventd.rc
~ # ls /
boot etc sd-ext
cache init sdcard
charger init.rc sys
data misc system
datadata proc tmp
default.prop res ueventd.espresso.rc
dev root ueventd.goldfish.rc
emmc sbin ueventd.rc
~ # ls /boot/
~ # du -hs
So, now my internal SD card has (or I think it has) a partition that looks like this
Code:
1 17.4kB 7000MB 7000MB fat32 msftres
2 7000MB 7400MB 400MB ext2
3 7400MB 7818MB 418MB linux-swap(v1)
This clearly didn't sit well with it. It no longer boots, no screen, no nothing. No download mode. When I plug it into the computer and start it, I get a brief moment where it starts to act like a USB device, then disappears, then restarts. ADB can't see it.
I'm pretty sure I'm screwed here. I've tried Odin and Heimdall, on ubuntu, XP, win7. None can reach the device.
Is there any chance I can get this to run by creating an external SD card with the correct partitions on it? I read a few posts where people were able to run a device that had a corrupt SD internal card on the external one.
Any help greatly appreciated.
Click to expand...
Click to collapse
atomatomatomatom said:
Hard would be better than my current state of 'impossible' - how did you get it into download mode? I read that people hold it down for ages and it sometimes works. I suspect this may be a cruel joke - poor suckers sitting there holding their dead tablet for days on end.
Click to expand...
Click to collapse
what did you mean by cruel joke ? it is happening to me right now and i want to know if there is any solution for this..
my parents would've kill me if they know
---------- Post added at 08:39 PM ---------- Previous post was at 08:30 PM ----------
PanchoPlanet said:
Time for a new tab.
Or maybe you can use Hemidall /Linux ADB to setup original partitions.
Google is your friend.
Pp.
Click to expand...
Click to collapse
what did you mean by using hemiball / linux adb ?
please teach me how because i really want to have my tab alive back

Kowyim said:
what did you mean by cruel joke ? it is happening to me right now and i want to know if there is any solution for this..
my parents would've kill me if they know
Click to expand...
Click to collapse
you said you can get it into download mode, but that it was 'hard' to get it into download mode. my device doesn't even go into download mode.
the cruel joke bit was that i read holding down the power/vol down for ages might bring it back into download mode eventually. but how long. 10 minutes, 1 hour, 1 day, 1 week?
if your tablet boots and shows anything on the display, you can probably get it into download mode. then just follow one of the guides that tells you how to restore it it to stock firmware.

atomatomatomatom said:
you said you can get it into download mode, but that it was 'hard' to get it into download mode. my device doesn't even go into download mode.
the cruel joke bit was that i read holding down the power/vol down for ages might bring it back into download mode eventually. but how long. 10 minutes, 1 hour, 1 day, 1 week?
if your tablet boots and shows anything on the display, you can probably get it into download mode. then just follow one of the guides that tells you how to restore it it to stock firmware.
Click to expand...
Click to collapse
hard means i need to do it over and over till i get into the recovery or download mode. i wish i could post a video about it but too bad i dont have a phone that can record..
our problem is the same i think because we tried to delete and recreate partition. now i cant even mount sd card (internal) because of the attempt of swapping.

thanks, perhaps i'll try again to get into download mode. so, you just keep trying. how long do you wait before retrying it? i hold power down, then also power on, and i see nothing. i don't know how long to hold it down before retying - or if i should do anything else in the meantime.
my understanding is you need to use odin or heimdall to restore the whole device, including the partition table. if you can get it into download mode, then you plug it into the computer and transfer the image from there. i would start with the stock one from http://www.sammobile.com/firmwares/
i can't find the instructions right now, but if your partition is altered, i think you want to find a PIT file for your device as well as restore the firmware.

atomatomatomatom said:
you said you can get it into download mode, but that it was 'hard' to get it into download mode. my device doesn't even go into download mode.
the cruel joke bit was that i read holding down the power/vol down for ages might bring it back into download mode eventually. but how long. 10 minutes, 1 hour, 1 day, 1 week?
if your tablet boots and shows anything on the display, you can probably get it into download mode. then just follow one of the guides that tells you how to restore it it to stock firmware.
Click to expand...
Click to collapse
atomatomatomatom said:
thanks, perhaps i'll try again to get into download mode. so, you just keep trying. how long do you wait before retrying it? i hold power down, then also power on, and i see nothing. i don't know how long to hold it down before retying - or if i should do anything else in the meantime.
my understanding is you need to use odin or heimdall to restore the whole device, including the partition table. if you can get it into download mode, then you plug it into the computer and transfer the image from there. i would start with the stock one from http://www.sammobile.com/firmwares/
i can't find the instructions right now, but if your partition is altered, i think you want to find a PIT file for your device as well as restore the firmware.
Click to expand...
Click to collapse
it was around 1-2 minute. if it doesn't work then i will restart and retry till i get into.
---------- Post added at 11:52 PM ---------- Previous post was at 11:33 PM ----------
atomatomatomatom said:
thanks, perhaps i'll try again to get into download mode. so, you just keep trying. how long do you wait before retrying it? i hold power down, then also power on, and i see nothing. i don't know how long to hold it down before retying - or if i should do anything else in the meantime.
my understanding is you need to use odin or heimdall to restore the whole device, including the partition table. if you can get it into download mode, then you plug it into the computer and transfer the image from there. i would start with the stock one from http://www.sammobile.com/firmwares/
i can't find the instructions right now, but if your partition is altered, i think you want to find a PIT file for your device as well as restore the firmware.
Click to expand...
Click to collapse
OMG OMG OMG did you have skype ?
omg you helped me !
i must repay you ! please add my skype - koyimz

that is great. glad you got yours fixed.
i'll try holding down my buttons for longer and hope that something comes up!

atomatomatomatom said:
thanks, perhaps i'll try again to get into download mode. so, you just keep trying. how long do you wait before retrying it? i hold power down, then also power on, and i see nothing. i don't know how long to hold it down before retying - or if i should do anything else in the meantime.
my understanding is you need to use odin or heimdall to restore the whole device, including the partition table. if you can get it into download mode, then you plug it into the computer and transfer the image from there. i would start with the stock one from http://www.sammobile.com/firmwares/
i can't find the instructions right now, but if your partition is altered, i think you want to find a PIT file for your device as well as restore the firmware.
Click to expand...
Click to collapse
awwww i thought that i have it fixed . but it stuck at the samsung logo and when i open recovery mode and try to wipe data it says e: unknown volume for path [/sd-ext] . but it says the data wipe complete and no fail except the sd-ext thing. any idea how to fix this ??

well, i fixed it. the rather harsh way. ebayed a used main board ($20), after shipping and exchange rates it came to about $40 canadian.
i might try hacking the old board open to see if i can scrape off the brain-dead SD card and see if that will force it to boot on the external card. but that is just for 'fun' now.

Thanks for the " Don't mess with the partitions " lesson you gave the forum.
Lol.
Pp.

ha. yeah, won't do that again.
i started going down the rabbit hole of trying to learn how to flash the OMAP4430 back into a booting state, but after wasting about 2 days i realized this was a total waste of my time when i could replace the board (or buy a new tablet) for the amount of time i had spent on it. boooooooo. but still burns!

Repartition - Need help adding more space to Internal Storage (Apps)

Hello,
I just bought a Gionee Elife E7.
I have a 4.4.2 custom ROM running on it, and everything works flawlessly, except I need more space on my Internal Storage from apps
After looking through various guides I'm stuck at this point:
Code:
Partition Table: gpt
Number Start End Size File system Name Flags
1 67.1MB 134MB 67.1MB fat16 modem
2 134MB 135MB 524kB sbl1
3 135MB 135MB 32.8kB dbi
4 201MB 201MB 32.8kB DDR
5 268MB 279MB 10.5MB aboot
6 279MB 279MB 512kB rpm
7 336MB 357MB 21.0MB boot
8 403MB 403MB 512kB tz
9 403MB 404MB 1049kB pad
10 404MB 406MB 1573kB modemst1
11 406MB 407MB 1573kB modemst2
12 470MB 1812MB 1342MB ext4 system
13 1812MB 6107MB 4295MB ext4 userdata
14 6107MB 6140MB 33.6MB ext4 persist
15 6140MB 6543MB 403MB ext4 cache
16 6543MB 6564MB 21.0MB recovery
17 6564MB 6566MB 1573kB fsg
18 6577MB 6577MB 1024B fsc
19 6577MB 6577MB 8192B ssd
20 6577MB 30.9GB 24.4GB fat32 udisk
21 30.9GB 30.9GB 10.5MB splash
22 30.9GB 31.3GB 322MB grow
The partition 13 "userdata" seems to be my partition for apps and the partition 20 "udisk" is my storage for files only.
Do I need to delete all the partitions from 13 to 20 in order to extend userdata from 4295MB to 8192MB and then proceed to add 14-20 again?
Also if I performed a full backup in twrp and moved it to my PC, is it still risky to do this?

How can I backup Soyes XS ROM?

I received my Soyes XS (the 2GB+16GB model) today. Before I start tinkering with it, I would like to make a full backup of the ROM.
The device uses a MTK chip (MT6737?). I tried to google for a scatter file (for SP Flash Tool) for the device, but so far I have not found one. I could try to make a scatter file myself, if I can get the partition offsets and sizes, but so far I have not been able to do that. The device has no /proc/partinfo file and /proc/mtd is empty. Does anybody know how can I determine the partition structure (start offsets and sizes) so that I can make a scatter file?
Or is there any other way to backup the ROM?

I found file MT6737M_Android_scatter.txt from https://raphsonbd.com/mediatek-device-android-scatter-file/
From that file I got the starting offset (0x0) and length (0x80000) of the PGPT partition, which contains the GPT partition table, which contains start sectors and sizes for all of the partitions of my device.
So I started SP Flash Tool and used "Read Back" to read the PGPT partition to my Linux PC to file PGPT. There I issued command "sgdisk -p PGPT", which displayed the following information:
Code:
$ sgdisk -p PGPT
Warning! Disk size is smaller than the main header indicates! Loading
secondary header from the last sector of the disk! You should use 'v' to
verify disk integrity, and perhaps options on the experts' menu to repair
the disk.
Caution: invalid backup GPT header, but valid main header; regenerating
backup header from main header.
Warning! Error 25 reading partition table for CRC check!
Warning! One or more CRCs don't match. You should repair the disk!
Main header: OK
Backup header: ERROR
Main partition table: OK
Backup partition table: ERROR
****************************************************************************
Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk
verification and recovery are STRONGLY recommended.
****************************************************************************
Disk /home/Big/tmp/Soyes XS/PGPT: 1024 sectors, 512.0 KiB
Sector size (logical): 512 bytes
Disk identifier (GUID): 00000000-0000-0000-0000-000000000000
Partition table holds up to 23 entries
Main partition table begins at sector 2 and ends at sector 7
First usable sector is 1024, last usable sector is 61070335
Partitions will be aligned on 1024-sector boundaries
Total free space is 0 sectors (0 bytes)
Number Start (sector) End (sector) Size Code Name
1 1024 7167 3.0 MiB 0700 proinfo
2 7168 17407 5.0 MiB 0700 nvram
3 17408 37887 10.0 MiB 0700 protect1
4 37888 58367 10.0 MiB 0700 protect2
5 58368 59391 512.0 KiB 0700 lk
6 59392 60415 512.0 KiB 0700 para
7 60416 93183 16.0 MiB 0700 boot
8 93184 125951 16.0 MiB 0700 recovery
9 125952 142335 8.0 MiB 0700 logo
10 142336 162815 10.0 MiB 0700 expdb
11 162816 163839 512.0 KiB 0700 seccfg
12 163840 167935 2.0 MiB 0700 oemkeystore
13 167936 180223 6.0 MiB 0700 secro
14 180224 196607 8.0 MiB 0700 keystore
15 196608 206847 5.0 MiB 0700 tee1
16 206848 217087 5.0 MiB 0700 tee2
17 217088 219135 1024.0 KiB 0700 frp
18 219136 284671 32.0 MiB 0700 nvdata
19 284672 360447 37.0 MiB 0700 metadata
20 360448 5603327 2.5 GiB 0700 system
21 5603328 6422527 400.0 MiB 0700 cache
22 6422528 61037567 26.0 GiB 0700 userdata
23 61037568 61070335 16.0 MiB 0700 flashinfo
Using that information I could use "Read Back" in SP Flash Tool to backup the partitions to my PC. The sector size is 512, so for example for the system partition I must enter 512*360448 = 184549376 as the Start Address and 512*(5603327-360448+1) = 2684354560 as the Length (in Decimal) when adding the partition to be read back.
By the way, the device should have only 16 GB memory, but the userdata partition is 26 GB! Strange!

Partition table 64gb version

Hi,
Accidentally I removed all partitions from Mix 2s 64GB. Would it be pissible to check and send me partition table? I am not able to do anything without partition. Fastboot works, so repartitation is possible, but have no table.
Thanks

up

Hi,
I hope it is not to late. Just yesterday I installed WinPE to my phone, so i made a Backup of the gparted print:
Code:
Number Start End Size File system Name Flags
1 0.02MB 0.04MB 0.02MB switch
2 0.04MB 0.07MB 0.03MB ssd
3 0.07MB 0.52MB 0.45MB bk01
4 0.52MB 0.79MB 0.26MB bk02
5 0.79MB 1.05MB 0.26MB bk03
6 1.05MB 1.57MB 0.52MB keystore
7 1.57MB 2.10MB 0.52MB frp
8 2.10MB 4.19MB 2.10MB bk04
9 4.19MB 8.39MB 4.19MB misc
10 8.39MB 16.8MB 8.39MB logfs
11 16.8MB 33.6MB 16.8MB oops
12 33.6MB 50.3MB 16.8MB devinfo
13 50.3MB 67.1MB 16.8MB bk05
14 67.1MB 134MB 67.1MB ext4 persist
15 134MB 201MB 67.1MB ext4 persistbak
16 201MB 268MB 67.1MB logdump
17 268MB 403MB 134MB minidump
18 403MB 1275MB 872MB ext4 cust
19 1275MB 1342MB 67.1MB recovery
20 1342MB 1611MB 268MB ext4 cache
21 1611MB 59064MB 57454MB ext4 userdata

ElTentakel said:
Hi,
I hope it is not to late. Just yesterday I installed WinPE to my phone, so i made a Backup of the gparted print:
Code:
Number Start End Size File system Name Flags
1 0.02MB 0.04MB 0.02MB switch
2 0.04MB 0.07MB 0.03MB ssd
3 0.07MB 0.52MB 0.45MB bk01
4 0.52MB 0.79MB 0.26MB bk02
5 0.79MB 1.05MB 0.26MB bk03
6 1.05MB 1.57MB 0.52MB keystore
7 1.57MB 2.10MB 0.52MB frp
8 2.10MB 4.19MB 2.10MB bk04
9 4.19MB 8.39MB 4.19MB misc
10 8.39MB 16.8MB 8.39MB logfs
11 16.8MB 33.6MB 16.8MB oops
12 33.6MB 50.3MB 16.8MB devinfo
13 50.3MB 67.1MB 16.8MB bk05
14 67.1MB 134MB 67.1MB ext4 persist
15 134MB 201MB 67.1MB ext4 persistbak
16 201MB 268MB 67.1MB logdump
17 268MB 403MB 134MB minidump
18 403MB 1275MB 872MB ext4 cust
19 1275MB 1342MB 67.1MB recovery
20 1342MB 1611MB 268MB ext4 cache
21 1611MB 59064MB 57454MB ext4 userdata
Click to expand...
Click to collapse
Is it the same with mix 3 since it's basically similar phone?
I corrupted my partition

I have the same issue where I wiped everything like an idiot, how do I apply the partition table to the phone, what are the steps?