XDA Xposed Tuesday: XHangouts Will Improve Your Hangouts

Ever since Google started supporting text messaging in Hangouts many people have … more

Shattered Screen? Turn Your Broken Device into a Complete Media Center!

A cracked screen usually means you’ll have to spend a hefty … more

Gmail 5.0: Material Design and Multiple Account Support

Google started to materialize many of its applications right after announcing the … more

Some of Our Favorite Features in Android 5.0 Lollipop

Android 5.0 Lollipop is the latest major revision to Google’s mobile operating … more
Post Reply

[Q] Partition Table & Mount Point List

OP YishaiN

14th January 2012, 12:37 PM   |  #1  
OP Junior Member
Thanks Meter: 0
 
1 posts
Join Date:Joined: Jan 2012
Hi all

I am using a Galaxy Note GT-N7000 2.3.6 N7000XXKK5 (Hungerian) 2.6.35.7-N7000XXKKA-...

I was wondring if there is a way to view the device list in the partition table and there mount points.

I understand in older versions of android "cat /proc/mtd" would produce a table like this:
dev: size erasesize name
mtd0: 000a0000 00020000 "misc"
mtd1: 00480000 00020000 "recovery"
mtd2: 00300000 00020000 "boot"
mtd3: 0fa00000 00020000 "system"
mtd4: 02800000 00020000 "cache"
mtd5: 093a0000 00020000 "userdata"

I see now the mount points have moved to "/dev/block" but I can not get there names.
I have seen many assesments of some of the "mmcblk0p0-13" names, but nothing looked like an orgenized list of the "Partition Information Table".
Can anyone tell me how I can printout a table like above on SGN.

I would like to use the "dd" command to create images of all the partitions before I start messing with my phone.

If anyone could help me with these commands I would mostly appreciate it.

"dd if=/dev/block/mmcblk0p? of=/sdcard/???.img bs=4096"
(for all mmcblk0p? and there names ???.img)
and if possible to printout the partition table using "cat /dev/block/???" or anything else.

I fund ths on the "[INFO][DEV]SGS2 Epic 4G Touch Partition Structure"
http://forum.xda-developers.com/show....php?t=1278281

--- Entry #0 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 0
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name: GANG
Filename: emmc.img

--- Entry #1 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 1
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name: BOOT
Filename: boot.bin

--- Entry #2 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 4
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 8192
Partition Block Count: 40960
Unknown 2: 0
Unknown 3: 0
Partition Name: EFS
Filename: efs.img

--- Entry #3 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 2
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 49152
Partition Block Count: 2560
Unknown 2: 0
Unknown 3: 0
Partition Name: SBL1
Filename: Sbl.bin

--- Entry #4 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 3
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 53248
Partition Block Count: 2560
Unknown 2: 0
Unknown 3: 0
Partition Name: SBL2
Filename:

--- Entry #5 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 5
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 57344
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: PARAM
Filename: param.lfs

--- Entry #6 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 6
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 73728
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: KERNEL
Filename: zImage

--- Entry #7 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 7
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 90112
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: RECOVERY
Filename: recovery.bin

--- Entry #8 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 8
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 106496
Partition Block Count: 614400
Unknown 2: 0
Unknown 3: 0
Partition Name: CACHE
Filename: cache.img

--- Entry #9 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 9
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 720896
Partition Block Count: 32768
Unknown 2: 0
Unknown 3: 0
Partition Name: MODEM
Filename: modem.bin

--- Entry #10 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 10
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 753664
Partition Block Count: 1048576
Unknown 2: 0
Unknown 3: 0
Partition Name: FACTORYFS
Filename: factoryfs.img

--- Entry #11 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 11
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 1802240
Partition Block Count: 4194304
Unknown 2: 0
Unknown 3: 0
Partition Name: DATAFS
Filename: data.img

--- Entry #12 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 12
Partition Flags: 2 (R/W)
Unknown 1: 0
Partition Block Size: 5996544
Partition Block Count: 24133632
Unknown 2: 0
Unknown 3: 0
Partition Name: UMS
Filename:

--- Entry #13 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 13
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 30130176
Partition Block Count: 638976
Unknown 2: 0
Unknown 3: 0
Partition Name: HIDDEN
Filename: hidden.img

--- Entry #14 ---
Unused: Yes
Partition Type: 1 (Unknown)
Partition Identifier: 9
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name:
Filename:
Ending session...
Rebooting device...

I was wondering if i could find something like that for SGN


Best Regards & Thanks
Yishai
Last edited by YishaiN; 14th January 2012 at 12:50 PM.
13th August 2012, 01:21 PM   |  #2  
Senior Member
Thanks Meter: 12
 
134 posts
Join Date:Joined: Jan 2011
+1
yes it would be nice to know that. Then if it possible to use dd commands, then we will can flash custom kernels much easier and maybe make linux running nativeky if we get kernek source. Sorry for bad english.
14th August 2012, 02:38 AM   |  #3  
Member
Thanks Meter: 19
 
99 posts
Join Date:Joined: May 2012
Donate to Me
More
Well, you can get the basic partitions from /proc/mounts :
Code:
  -> adb shell cat /proc/mounts | grep /dev/block
/dev/block/mmcblk0p9 /system ext4 ro,relatime,barrier=1,noauto_da_alloc 0 0
/dev/block/mmcblk0p7 /cache ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=0,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p10 /data ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=0,noauto_da_alloc 0 0
/dev/block/mmcblk0p12 /preload ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p1 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p4 /mnt/.lfs j4fs rw,relatime 0 0
/dev/block/vold/259:3 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
..............
15th August 2012, 09:27 PM   |  #4  
Senior Member
Thanks Meter: 12
 
134 posts
Join Date:Joined: Jan 2011
cat /proc/mounts and partitions doesn't show where is recovery.img. and no cat/proc/mtd in /proc. So how to know where is recovery.img?
16th August 2012, 11:43 AM   |  #5  
badge2033's Avatar
Senior Member
Flag Monastir
Thanks Meter: 62
 
163 posts
Join Date:Joined: Mar 2011
More
using adb
Code:
adb shell parted /dev/block/mmcblk0
using terminal emulator on the phone
Code:
su
parted /dev/block/mmcblk0
and then command: print
Last edited by badge2033; 16th August 2012 at 12:43 PM. Reason: then command: print
14th January 2013, 11:18 AM   |  #6  
Member
Thanks Meter: 10
 
86 posts
Join Date:Joined: May 2011
N7000 ................

dev: size erasesize name
mmcblk0p1: 001500000 000000 "efs"
mmcblk0p2: 000147c00 000000 "sbl1"
mmcblk0p3: 000147c00 000000 "sbl2"
mmcblk0p4: 000831400 000000 "param"
mmcblk0p5: 000831400 000000 "boot"
mmcblk0p6: 000831400 000000 "recovery"
mmcblk0p7: 00d200000 000000 "cache"
mmcblk0p8: 0010ccccd 000000 "modem"
mmcblk0p9: 037d00000 000000 "system"
mmcblk0p10: 086300000 000000 "userdata"
mmcblk0p11: 2f999999a 000000 "emmc"
mmcblk0p12: 021900000 000000 "hidden"

---------- Post added at 12:18 PM ---------- Previous post was at 11:53 AM ----------

please ask where bs = 4096 ?????????????????/
18th January 2014, 09:26 PM   |  #7  
SaurusM3's Avatar
Member
Flag daLLas
Thanks Meter: 10
 
49 posts
Join Date:Joined: Dec 2012
More
Quote:
Originally Posted by thinh182009

N7000 ................

---------- Post added at 12:18 PM ---------- Previous post was at 11:53 AM ----------

[please ask where bs = 4096 ?????????????????/

Since your question is off-topic, I'll keep it short -

bs (block size) in the 'dd' command is actually the cpu buffer size used during data transport between devices. If not specified, default is 512 bytes. Each respective hardware driver then buffers I/O data between the cpu and its dependent device. 4096 is probably a good number for Android.
6th February 2014, 06:40 PM   |  #8  
Junior Member
Thanks Meter: 0
 
1 posts
Join Date:Joined: Dec 2012
on Nexus 7 flo and maybe other devices:

/dev/block/mmcblk0p14 boot.img
/dev/block/mmcblk0p22 system.img
Last edited by cowlinator; 6th February 2014 at 06:46 PM.

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes