Database Develop

Partition Table? Post plz

Can someone post the partition table block for me thanks. Need to see which one is SYSTEM, CACHE AND USERDATA.

@hatememarkz you are a d/a
@...awesome... hope this helps
Partition Table
/dev/block/mmcblk0p1 secboot2 partition map
/dev/block/mmcblk0p2 dbl.mbn (boot loader)
/dev/block/mmcblk0p3 osbl.mbn (boot loader)
/dev/block/mmcblk0p4 MBR extended partition table
/dev/block/mmcblk0p5 EMMCBOOT.MBN (boot loader, has odin download mode)
/dev/block/mmcblk0p6 amss.mbn
/dev/block/mmcblk0p7 emmcparam.bin
/dev/block/mmcblk0p8 boot.img (linux kernel)
/dev/block/mmcblk0p9 adsp.mbn (baseband)
/dev/block/mmcblk0p10 rmt
/dev/block/mmcblk0p11 rmt
/dev/block/mmcblk0p12 persist.ext4
/dev/block/mmcblk0p13 recovery.img (linux kernel+initrd for recovery mode)
/dev/block/mmcblk0p14 param
/dev/block/mmcblk0p15 system.ext4
/dev/block/mmcblk0p16 cache.ext4
/dev/block/mmcblk0p17 data.ext4
/dev/block/mmcblk0p18 preload.ext4
/dev/block/mmcblk0p19
/dev/block/mmcblk0p20 all 0's
/dev/block/mmcblk0p21 all 0's
/dev/block/mmcblk0p22 all 0's
/dev/block/mmcblk0p23 all 0's
/dev/block/mmcblk0p24 all 0's
/dev/block/mmcblk0p25 all 0's
/dev/block/mmcblk0p26 all 0's
/dev/block/mmcblk0p27 efs (encrypted fs)
/dev/block/mmcblk0p28 /mnt/sdcard

Thread Closed as per OP request, Thank You.

[Q] About the partitions

Hello.
There are 12 partitions on LGP970 v30c phone.
Partitions Name
/dev/block/mmcblk0p1 = x-loader
/dev/block/mmcblk0p2 = u-boot
/dev/block/mmcblk0p3 = boot
/dev/block/mmcblk0p4 = recovery
/dev/block/mmcblk0p5 = lgdrm
/dev/block/mmcblk0p6 = divxkey
/dev/block/mmcblk0p7 = fota
/dev/block/mmcblk0p8 = system
/dev/block/mmcblk0p9 = data
/dev/block/mmcblk0p10 = cache
/dev/block/mmcblk0p11 = nv
/dev/block/mmcblk0p12 = misc
1.does anyone know what the lgdrm, divxkey and nv partitions are used for? And how can we intepret them.
2.There are two other hardware partition mmcblk0boot0 and mmcblk0boot1. When i open them with a hex editor, its just all zeros.
What is the purpose of these two partition?
Any help would greatly be appreciated. Thank you!

[Q] sm-g730a recovery help

I'm trying to build a recovery for the first time for this device and i was wondering if someone could look at my recovery.fstab and help me out with it. i found lots of tutorials on building cwm for a new device but editing the recovery.fstab and boardconfig.mk i havnt found really anything.
recovery.fstab
# mount point fstype device [device2]
/boot emmc /dev/block/mmcblk0p13
/cache ext4 /dev/block/mmcblk0p21
/data ext4 /dev/block/mmcblk0p23
/recovery emmc /dev/block/mmcblk0p14
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/system ext4 /dev/block/mmcblk0p20
/sd-ext ext4 ?
---------------
boardconfig.mk
USE_CAMERA_STUB := true
# inherit from the proprietary version
-include vendor/samsung/s3mini/BoardConfigVendor.mk
TARGET_ARCH := arm
TARGET_NO_BOOTLOADER := true
TARGET_BOARD_PLATFORM := unknown
TARGET_CPU_ABI := armeabi-v7a
TARGET_CPU_ABI2 := armeabi
TARGET_ARCH_VARIANT := armv7-a-neon
ARCH_ARM_HAVE_TLS_REGISTER := true
TARGET_BOOTLOADER_BOARD_NAME := s3mini
BOARD_KERNEL_CMDLINE := console=null androidboot.hardware=qcom user_debug=31
BOARD_KERNEL_BASE := 0x80200000
BOARD_KERNEL_PAGESIZE := 2048
# fix this up by examining /proc/mtd on a running device
BOARD_BOOTIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_FLASH_BLOCK_SIZE := 131072
TARGET_PREBUILT_KERNEL := device/samsung/s3mini/kernel
BOARD_HAS_NO_SELECT_BUTTON := true
-------------------
used:
ls -l /dev/block/platform/msm_sdcc.1/by-name > /mnt/sdcard/partitions.txt
partitions are as follow:
lrwxrwxrwx root root 2013-01-02 01:11 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-01-02 01:11 backup -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2013-01-02 01:11 boot -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2013-01-02 01:11 cache -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2013-01-02 01:11 efs -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2013-01-02 01:11 fota -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2013-01-02 01:11 fsg -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2013-01-02 01:11 hidden -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2013-01-02 01:11 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-01-02 01:11 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2013-01-02 01:11 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2013-01-02 01:11 pad -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-01-02 01:11 param -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2013-01-02 01:11 persist -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2013-01-02 01:11 recovery -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2013-01-02 01:11 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2013-01-02 01:11 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-01-02 01:11 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-01-02 01:11 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-01-02 01:11 ssd -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2013-01-02 01:11 system -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2013-01-02 01:11 tz -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-01-02 01:11 userdata -> /dev/block/mmcblk0p23
EDIT: I think i understand the recovery.fstab

I unpacked a stock-recovery.img from another post and got a recovery.fstab, can someone help me understand it?
# mount point fstype device [device2]
/boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot
/system ext4 /dev/block/platform/msm_sdcc.1/by-name/system
/data ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata length=-16384
/cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache
/recovery emmc /dev/block/platform/msm_sdcc.1/by-name/recovery
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/efs ext4 /dev/block/platform/msm_sdcc.1/by-name/efs
/modem emmc /dev/block/platform/msm_sdcc.1/by-name/modem
/preload ext4 /dev/block/platform/msm_sdcc.1/by-name/hidden

assassinanex said:
I unpacked a stock-recovery.img from another post and got a recovery.fstab, can someone help me understand it?
# mount point fstype device [device2]
/boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot
/system ext4 /dev/block/platform/msm_sdcc.1/by-name/system
/data ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata length=-16384
/cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache
/recovery emmc /dev/block/platform/msm_sdcc.1/by-name/recovery
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/efs ext4 /dev/block/platform/msm_sdcc.1/by-name/efs
/modem emmc /dev/block/platform/msm_sdcc.1/by-name/modem
/preload ext4 /dev/block/platform/msm_sdcc.1/by-name/hidden
Click to expand...
Click to collapse
intended_mount_location type partition
by-name doesn't always exists, you'll need to check what initfs is creating on your particular phone. The opensource kernel is available for your phone from samsung, best place to look imo.
PS. if this helps you I'd appreciate a copy of the firmware from your phone for a project
m0tter

any updates on this?

m0tter said:
intended_mount_location type partition
by-name doesn't always exists, you'll need to check what initfs is creating on your particular phone. The opensource kernel is available for your phone from samsung, best place to look imo.
PS. if this helps you I'd appreciate a copy of the firmware from your phone for a project
m0tter
Click to expand...
Click to collapse
if you need s3 mini sm-g730a firmware how do i exctract it ? ill send nmine to any who need

[Q] Creating partition images on 870A

Does anyone know the relation of which block devices in /dev/mmcblk0pXX belong to which partition? (ex: system, modem, boot, etc)
I'm looking to create a custom Odin AIO package for my install of lollipop, which has been rooted and such; going back to NE4 is a PITA and would like a faster route for when a full wipe is required.
Thanks in advance :good:

After scrounging the internet for awhile, I was able to answer my own question. I've posted the partition scheme below for others who might need it someday:
aboot -> /dev/block/mmcblk0p6
apnhlos -> /dev/block/mmcblk0p1
backup -> /dev/block/mmcblk0p18
boot -> /dev/block/mmcblk0p15
cache -> /dev/block/mmcblk0p24
dbi -> /dev/block/mmcblk0p4
ddr -> /dev/block/mmcblk0p5
efs -> /dev/block/mmcblk0p12
fota -> /dev/block/mmcblk0p17
fsc -> /dev/block/mmcblk0p19
fsg -> /dev/block/mmcblk0p9
modem -> /dev/block/mmcblk0p2
modemst1 -> /dev/block/mmcblk0p13
modemst2 -> /dev/block/mmcblk0p14
pad -> /dev/block/mmcblk0p10
param -> /dev/block/mmcblk0p11
persdata -> /dev/block/mmcblk0p22
persist -> /dev/block/mmcblk0p21
recovery -> /dev/block/mmcblk0p16
rpm -> /dev/block/mmcblk0p7
sbl1 -> /dev/block/mmcblk0p3
ssd -> /dev/block/mmcblk0p20
system -> /dev/block/mmcblk0p23
tz -> /dev/block/mmcblk0p8
userdata -> /dev/block/mmcblk0p25

[HELP] What happened here? Hardbrick after partitioning?

My device: MotoX (ghost)
Hey guys,
Today i pushed "parted" to my /sbin, chmodded 0755 and removed/recreated my userdata partition removing 5mb of total.. (to try to solve a known encryption bug of CM). Then, i reboot.
Now MY PHONE LOOKS HARD BRICKED!
How it is possible? i just deleted/recreated the userdata partition,
yes parted create on format ext2, but the next step is to convert to ext4 > f2fs..
but my phone does not start!
Black screen
No fastboot
lsusb does not list the usb connection..
Pressing the ON = doesn't boot
Pressing vol down + power = doesn't boot
Inserting charger = doesn't boot
No Lights on.
Battery is ok (i think), i started working w/ 100%.
full log of my actions here:
Code:
$ adb push sdparted/parted /sbin
3067 KB/s (346680 bytes in 0.110s)
~/droid $ adb shell
~ # ls
boot init.qcom.sh sepolicy
cache init.rc sideload
charger init.recovery.qcom.rc supersu
data license sys
default.prop proc system
dev property_contexts tmp
etc recovery twres
file_contexts res ueventd.qcom.rc
fstab.qcom root ueventd.rc
init sbin usb-otg
init.mmi.boot.sh sdcard
init.mmi.touch.sh seapp_contexts
~ # chmod 0755 /sbin/parted
~ # 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 SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 105MB 105MB ext4 modem
2 105MB 107MB 1536kB sbl1
3 107MB 108MB 1536kB sbl2
4 108MB 109MB 526kB sbl3
5 110MB 111MB 524kB aboot
6 112MB 112MB 145kB rpm
7 112MB 112MB 215kB tz
8 113MB 113MB 524kB utags
9 113MB 114MB 1049kB logs
10 114MB 117MB 3150kB padA
11 117MB 119MB 1536kB sbl2Backup
12 119MB 121MB 2097kB sbl3Backup
13 121MB 123MB 1536kB abootBackup
14 123MB 123MB 512kB rpmBackup
15 123MB 124MB 512kB tzBackup
16 124MB 124MB 524kB utagsBackup
17 124MB 126MB 1671kB padB
18 126MB 129MB 3146kB modemst1
19 129MB 132MB 3146kB modemst2
20 132MB 134MB 2097kB mbl
21 134MB 135MB 655kB hob
22 135MB 135MB 8192B dhob
23 135MB 143MB 8389kB ext4 persist
24 143MB 143MB 8192B ssd
25 143MB 147MB 3146kB ext2 fsg
26 147MB 148MB 1049kB sp
27 148MB 148MB 524kB misc
28 148MB 151MB 3146kB ext3 pds
29 151MB 151MB 131kB cid
30 151MB 156MB 4194kB logo
31 156MB 160MB 4194kB clogo
32 160MB 161MB 1049kB devtree
33 161MB 171MB 10.5MB boot
34 171MB 182MB 10.5MB recovery
35 182MB 190MB 8389kB kpan
36 190MB 1257MB 1067MB cache
37 1257MB 1258MB 1049kB padC
38 1258MB 2869MB 1611MB ext4 system
39 2869MB 2982MB 113MB customize
40 2982MB 15.8GB 12.8GB userdata
(parted) rm 40
rm 40
(parted) mkpartfs primary ext2 2982MB 15695MB
mkpartfs primary ext2 2982MB 15695MB
(parted) name 40 userdata
name 40 userdata
(parted) quit
quit
Information: You may need to update /etc/fstab.
.. and rebooted using twrp reboot/system button.
Wtf is happened?
any ideas how to solve this?
thanks.

Umm, gpt.bin corrupted.. Head towards the unbrick thread..