P769 MMC Mount Points

Search This thread
By:
Advanced…
S

saturnianalien

Member
Mar 1, 2013
31
12
33
Sacramento, CA
Code: 
179 MMC Devices and Mount Points

0	mmcblk0			3784704
1	mmcblk0p1		384
2	mmcblk0p2		1024
3	mmcblk0p3		10240
4	mmcblk0p4		10240
5	mmcblk0p5		5120		/dvp rw,nosuid,nodev,noatime - ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/divxkey rw,barrier=1,data=ordered
6	mmcblk0p6		512
7	mmcblk0p7		512
8	mmcblk0p8		20480
9	mmcblk0p9		512
10	mmcblk0p10		1024000		/system ro,relatime - ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/system ro,barrier=1,data=ordered
11	mmcblk0p11		1918976		/data rw,nosuid,nodev,relatime - ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata rw,resuid=1000,barrier=1,data=ordered,noauto_da_alloc
12	mmcblk0p12		768000		/cache rw,nosuid,nodev,relatime - ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/cache rw,barrier=1,data=ordered
13	mmcblk0p13		7680		/persist rw,nosuid,nodev,noatime - ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/persist rw,barrier=1,data=ordered
14	mmcblk0p14		16384		/mpt rw,nosuid,nodev,relatime - ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/mlt rw,barrier=1,data=ordered,noauto_da_alloc
40	mmcblk0boot1		2048
20	mmcblk0boot0		2048
60	mmcblk1			7761920
61	mmcblk1p1		7761919		/mnt/sdcard/external_sd rw,nosuid,nodev,noexec,relatime - vfat /dev/block/vold/179:61 rw,dirsync,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro

0 Mount Points

1	/ ro,relatime - rootfs rootfs ro
3	/proc rw,relatime - proc proc relatime - devpts devpts rw,mode=600
12	/dev rw,nosuidrw
10	/dev/pts rw,,relatime - tmpfs tmpfs rw,mode=755
13	/sys rw,relatime - sysfs sysfs rw
14	/acct rw,relatime - cgroup none rw,cpuacct
15	/mnt/asec rw,relatime - tmpfs tmpfs rw,mode=755,gid=1000
16	/mnt/obb rw,relatime - tmpfs tmpfs rw,mode=755,gid=1000
17	/dev/cpuctl rw,relatime - cgroup none rw,cpu
18	/mnt/sdcard rw,nosuid,nodev,relatime - fuse /dev/fuse rw,user_id=1023,group_id=1023,default_permissions,allow_other
 
Last edited:
  • Like
Reactions: kuma82 and Lelus
S

saturnianalien

Member
Mar 1, 2013
31
12
33
Sacramento, CA
Catenated the partitions under /dev/block to binary files. You can download them all here. A few notes though. First is that I didn't included partition 5, 11, 12, 13, and 14 because these are specific to every user. Also, I didn't include partition 7 (aka the "nv" partition) because that has the IMEI in it. A few things that I noticed: partitions 5 and 7 are mostly NULL characters, while partitions boot0, boot1, 6, 8, and 9 are all NULL characters (verified this with checksums of empty files of equal length). I also didn't include these NULL partitions since you can just create NULL files anyway (in windows: fsutil file createnew filename.ext #ofbytes). Also, the paritions that weren't included are listed in the file "sizes.txt" with some information about them, including their sizes in KB. It makes sense that partition 9 be all NULL since it's "reserved", but I'm unsure of the others. I'm guessing that it's feeding me NULL characters instead because of a permission issue. The boot0 and boot1 are especially mysterious. Here are their associated names one more time:

Code: 
p1	x
p2	u
p3	boot
p4	recovery
p5	divxkey
p6	misc
p7	nv
p8	fota
p9	reserved
p10	system
p11	userdata
p12	cache
p13	persist
p14	mlt
boot1
boot0

Still haven't figured out what divxkey (partition 5) is for, but it changes all the time. Partition 6, misc, is supposed to be hardware settings, USB configuration, and carrier ID. But again, this partition was NULL upon feeding to a new file (probably a permission issue). Partition 7, nv, I can only gather contains important information like the IMEI. Partition 8, fota, must have something to do with the Firmware-Over-The-Air process. Probably a temporary area to download the firmware. Partition 11 is just your contacts, messages, settings, and apps while partition 12 is just your frequently accessed data and app components. Partition 13, or "persist", seems to be a thing that replaces swap. Under low memory conditions, android terminates the application but allows it to persist it's state through a series of callbacks. This way, it appears as though the app never restarted. Partition 14, mlt, I'm unsure of. Though, I did notice a process called "LG MLT". I can't help but think the two are correlated. Searching online I found several "answers". Some say that it's some kind of logging system, others say it's a management tool for LG roms, and one person even said it's HDMI over USB. I'm not really sure about this, but I'm with the opinion that it's some kind of logging system because it changes all the time.
 
Last edited:
  • Like
Reactions: Lelus and Tablechair
S

saturnianalien

Member
Mar 1, 2013
31
12
33
Sacramento, CA
Mapping

Catenated this from /proc/179/maps. This caught my eye, because somewhere in my abysmal Linux knowledge I vaguely remember that major number 0 (those other mount points in my first post) applies to something from address 00008000 to ffff1000.

Code: 
00008000-00009000 r-xp 00000000 b3:0a 350        /system/bin/lgdrmserver
00009000-0000a000 rw-p 00001000 b3:0a 350        /system/bin/lgdrmserver
002bb000-002ce000 rw-p 00000000 00:00 0          [heap]
10000000-10001000 ---p 00000000 00:00 0 
10001000-10100000 rw-p 00000000 00:00 0 
40007000-40008000 r--p 00000000 00:00 0 
4000a000-40037000 r-xp 00000000 b3:0a 1048       /system/lib/libutils.so
40037000-40039000 rw-p 0002d000 b3:0a 1048       /system/lib/libutils.so
40039000-40045000 r-xp 00000000 b3:0a 979        /system/lib/liblgsecclk.so
40045000-40047000 rw-p 0000c000 b3:0a 979        /system/lib/liblgsecclk.so
40056000-40163000 r-xp 00000000 b3:0a 969        /system/lib/liblgdrm.so
40163000-40173000 rw-p 0010d000 b3:0a 969        /system/lib/liblgdrm.so
40173000-40178000 rw-p 00000000 00:00 0 
40178000-4018f000 r-xp 00000000 b3:0a 1110       /system/lib/libz.so
4018f000-40190000 rw-p 00017000 b3:0a 1110       /system/lib/libz.so
40190000-401d3000 r-xp 00000000 b3:0a 893        /system/lib/libc.so
401d3000-401d6000 rw-p 00043000 b3:0a 893        /system/lib/libc.so
401d6000-401e1000 rw-p 00000000 00:00 0 
401e1000-401ee000 r--s 00000000 00:0c 1047       /dev/__properties__ (deleted)
401ee000-40203000 r-xp 00000000 b3:0a 984        /system/lib/libm.so
40203000-40204000 rw-p 00015000 b3:0a 984        /system/lib/libm.so
40204000-40207000 r-xp 00000000 b3:0a 982        /system/lib/liblog.so
40207000-40208000 rw-p 00003000 b3:0a 982        /system/lib/liblog.so
40208000-40217000 r-xp 00000000 b3:0a 914        /system/lib/libcutils.so
40217000-40218000 rw-p 0000f000 b3:0a 914        /system/lib/libcutils.so
40218000-40227000 rw-p 00000000 00:00 0 
40227000-40232000 r-xp 00000000 b3:0a 950        /system/lib/libhardware_legacy.so
40232000-40233000 rw-p 0000b000 b3:0a 950        /system/lib/libhardware_legacy.so
40233000-40234000 rw-p 00000000 00:00 0 
40234000-40236000 r-xp 00000000 b3:0a 1107       /system/lib/libwpa_client.so
40236000-40237000 rw-p 00002000 b3:0a 1107       /system/lib/libwpa_client.so
40237000-4023c000 r-xp 00000000 b3:0a 993        /system/lib/libnetutils.so
4023c000-4023d000 rw-p 00005000 b3:0a 993        /system/lib/libnetutils.so
4023f000-40240000 r-xp 00000000 b3:0a 1036       /system/lib/libstdc++.so
40240000-40241000 rw-p 00001000 b3:0a 1036       /system/lib/libstdc++.so
40241000-40264000 r-xp 00000000 b3:0a 886        /system/lib/libbinder.so
40264000-4026a000 rw-p 00023000 b3:0a 886        /system/lib/libbinder.so
4026a000-40368000 r--p 00000000 00:0c 3079       /dev/binder
b0001000-b0009000 r-xp 00001000 b3:0a 352        /system/bin/linker
b0009000-b000a000 rw-p 00009000 b3:0a 352        /system/bin/linker
b000a000-b0019000 rw-p 00000000 00:00 0 
bebdb000-bebfc000 rw-p 00000000 00:00 0          [stack]
ffff0000-ffff1000 r-xp 00000000 00:00 0          [vectors]
 
Last edited:
S

saturnianalien

Member
Mar 1, 2013
31
12
33
Sacramento, CA
Very glad to hear that Tablechair. :) Hopefully this knowledge will help us in more ways than one.

Anyways, I just figured out what the 1st and 2nd partitions are. The 1st partition, x (which stands for x-loader), is the OMAP4 primary bootloader and it uses three public keys: CertPK, CertPPA, and CertISW. Motorola phones used a similar thing with OMAP3. So, the 2nd partition, u, actually boostraps on the primary bootloader. This new bootloader is u-boot (it's open specification) and it uses CertISW. This then boots the kernel and ramdisk from the 3rd partition: boot.

Sent from my LG-P769 using xda app-developers app
 
Last edited:
  • Like
Reactions: Tablechair and sguerrini97
Tablechair

Tablechair

Senior Member
Feb 9, 2013
267
117
Waterbury CT
I took p1 p2 and p4 renamed them u-boot.img x-loader.img and recovery.img and flashed them just like that in fastboot and fixed my security error/boot loop problem.

Sent from my LG-P769 using xda app-developers app
 
  • Like
Reactions: saturnianalien
B

byt3b0mb

Senior Member
Oct 8, 2009
581
136
Seattle
Tablechair said:
I took p1 p2 and p4 renamed them u-boot.img x-loader.img and recovery.img and flashed them just like that in fastboot and fixed my security error/boot loop problem.

Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse


can you share those images? seems that the partitions.7z file is no longer available. does anyone have that? I am bricked, accidentally flashed uboot and cant restore with lg tool. PM if you can help thanks!
 
L

Lelus

Senior Member
Nov 18, 2009
494
434
Chicago
byt3b0mb said:
i got this phone to boot as normal again, trying to restore it or downgrade to 10a, but when it gets to s/w mode i keep getting usb device not recognized consistently in windows 7 & windows xp. any suggestions?
Click to expand...
Click to collapse

Not sure if i get it, does your phone boot normally ? you are on 10g trying to downgrade to 11a ?
what drivers are you using ?
 
Last edited:
B

byt3b0mb

Senior Member
Oct 8, 2009
581
136
Seattle
Lelus said:
Not sure if i get it, does you phone boot normally ? you are on 10g trying to downgrade to 11a ?
what drivers are you using ?
Click to expand...
Click to collapse

i was on 10g and trying to flash anything else -- got it fixed but have a new problem now - followed the jellybean bootloader unlock thread where you end up with a mirrored display and jacked up touch screen, couldnt unlock bootloader for some reason - now got restored to 10g but at initial power on the phone has the mirror display after a screen off and back on it looks normal, but the touch screen is still jacked up. i am trying to get it back to stock without the display issues. any suggestions?
 
Tablechair

Tablechair

Senior Member
Feb 9, 2013
267
117
Waterbury CT
To fix your touchscreen issue

Lelus said:
[Confirmed working]

Fortunately I was wrong and was able to extract touch firmware for p769 from kernel sources
I'm 100% sure it's the right firmware and will fix the problem.

unzip v6.bin to sdcard

adb shell
su
cat /sdcard/external_sd/v6.bin > /sys/devices/virtual/input/lge_touch/firmware
reboot
[Confirmed working]
Click to expand...
Click to collapse

You need to be rooted to do this. Its on like page 2 or 3 of this thread http://xdaforums.com/showthread.php?t=2182867&page=3
and is linked in the P769 bootloader unlock thread as it is part of that process. If your bootloader didn't unlock its because you didn't leave your phone on long enough before attempting unlock I think it has to be powered on for 30-60 min.

Lelus has also put together an easy way to flash your u-boot and x-loader back to stock which will fix your inverted boot screen. http://xdaforums.com/showpost.php?p=40121966&postcount=7
 
Last edited:
  • Like
Reactions: BajoPrimate
L

lecorbusier

Senior Member
Nov 28, 2012
1,111
120
Samsung Galaxy S5
LG G6
That is not that uncommon with Samsung Devices, which have PIT files for this. Otherwise danger of fully bricking the device is high. I thought this a good idea to shrink system partition and increase data partition. However, with CM12 or 13, one GB for system is no longer overly large.
 
You must log in or register to reply here.

Similar threads

mingkee
temporary LG L9 (P760 and P769) rooting/Q&A/accessories thread
Replies
1K
Views
352K
L
lecorbusier
carloswii5
[Guide]Unlock Bootloader for Noobs P769
Replies
2K
Views
305K
D
danygsm80
A
[TUTORIAL] ROOT LG Optimus L9 - EASY! (P760,P765,P768,P769)
Replies
141
Views
212K
S
SHAOLIN.DRAGON
L
[fastboot] l9 p760 p765 p768 p769
Replies
83
Views
171K
R
rethus
S
[BIN]{LGFlashTool} Unbrick/Unroot/Flash ANY (P769, MS769, P760) in Download Mode
Replies
135
Views
133K
S
STALKER18

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 2
    S
    saturnianalien
    Code: 
    179 MMC Devices and Mount Points

0	mmcblk0			3784704
1	mmcblk0p1		384
2	mmcblk0p2		1024
3	mmcblk0p3		10240
4	mmcblk0p4		10240
5	mmcblk0p5		5120		/dvp rw,nosuid,nodev,noatime - ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/divxkey rw,barrier=1,data=ordered
6	mmcblk0p6		512
7	mmcblk0p7		512
8	mmcblk0p8		20480
9	mmcblk0p9		512
10	mmcblk0p10		1024000		/system ro,relatime - ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/system ro,barrier=1,data=ordered
11	mmcblk0p11		1918976		/data rw,nosuid,nodev,relatime - ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata rw,resuid=1000,barrier=1,data=ordered,noauto_da_alloc
12	mmcblk0p12		768000		/cache rw,nosuid,nodev,relatime - ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/cache rw,barrier=1,data=ordered
13	mmcblk0p13		7680		/persist rw,nosuid,nodev,noatime - ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/persist rw,barrier=1,data=ordered
14	mmcblk0p14		16384		/mpt rw,nosuid,nodev,relatime - ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/mlt rw,barrier=1,data=ordered,noauto_da_alloc
40	mmcblk0boot1		2048
20	mmcblk0boot0		2048
60	mmcblk1			7761920
61	mmcblk1p1		7761919		/mnt/sdcard/external_sd rw,nosuid,nodev,noexec,relatime - vfat /dev/block/vold/179:61 rw,dirsync,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro

0 Mount Points

1	/ ro,relatime - rootfs rootfs ro
3	/proc rw,relatime - proc proc relatime - devpts devpts rw,mode=600
12	/dev rw,nosuidrw
10	/dev/pts rw,,relatime - tmpfs tmpfs rw,mode=755
13	/sys rw,relatime - sysfs sysfs rw
14	/acct rw,relatime - cgroup none rw,cpuacct
15	/mnt/asec rw,relatime - tmpfs tmpfs rw,mode=755,gid=1000
16	/mnt/obb rw,relatime - tmpfs tmpfs rw,mode=755,gid=1000
17	/dev/cpuctl rw,relatime - cgroup none rw,cpu
18	/mnt/sdcard rw,nosuid,nodev,relatime - fuse /dev/fuse rw,user_id=1023,group_id=1023,default_permissions,allow_other
    View
    2
    S
    saturnianalien
    Catenated the partitions under /dev/block to binary files. You can download them all here. A few notes though. First is that I didn't included partition 5, 11, 12, 13, and 14 because these are specific to every user. Also, I didn't include partition 7 (aka the "nv" partition) because that has the IMEI in it. A few things that I noticed: partitions 5 and 7 are mostly NULL characters, while partitions boot0, boot1, 6, 8, and 9 are all NULL characters (verified this with checksums of empty files of equal length). I also didn't include these NULL partitions since you can just create NULL files anyway (in windows: fsutil file createnew filename.ext #ofbytes). Also, the paritions that weren't included are listed in the file "sizes.txt" with some information about them, including their sizes in KB. It makes sense that partition 9 be all NULL since it's "reserved", but I'm unsure of the others. I'm guessing that it's feeding me NULL characters instead because of a permission issue. The boot0 and boot1 are especially mysterious. Here are their associated names one more time:

    Code: 
    p1	x
p2	u
p3	boot
p4	recovery
p5	divxkey
p6	misc
p7	nv
p8	fota
p9	reserved
p10	system
p11	userdata
p12	cache
p13	persist
p14	mlt
boot1
boot0

    Still haven't figured out what divxkey (partition 5) is for, but it changes all the time. Partition 6, misc, is supposed to be hardware settings, USB configuration, and carrier ID. But again, this partition was NULL upon feeding to a new file (probably a permission issue). Partition 7, nv, I can only gather contains important information like the IMEI. Partition 8, fota, must have something to do with the Firmware-Over-The-Air process. Probably a temporary area to download the firmware. Partition 11 is just your contacts, messages, settings, and apps while partition 12 is just your frequently accessed data and app components. Partition 13, or "persist", seems to be a thing that replaces swap. Under low memory conditions, android terminates the application but allows it to persist it's state through a series of callbacks. This way, it appears as though the app never restarted. Partition 14, mlt, I'm unsure of. Though, I did notice a process called "LG MLT". I can't help but think the two are correlated. Searching online I found several "answers". Some say that it's some kind of logging system, others say it's a management tool for LG roms, and one person even said it's HDMI over USB. I'm not really sure about this, but I'm with the opinion that it's some kind of logging system because it changes all the time.
    View
    2
    S
    saturnianalien
    Very glad to hear that Tablechair. :) Hopefully this knowledge will help us in more ways than one.

    Anyways, I just figured out what the 1st and 2nd partitions are. The 1st partition, x (which stands for x-loader), is the OMAP4 primary bootloader and it uses three public keys: CertPK, CertPPA, and CertISW. Motorola phones used a similar thing with OMAP3. So, the 2nd partition, u, actually boostraps on the primary bootloader. This new bootloader is u-boot (it's open specification) and it uses CertISW. This then boots the kernel and ramdisk from the 3rd partition: boot.

    Sent from my LG-P769 using xda app-developers app
    View
    1
    Tablechair
    Tablechair
    I took p1 p2 and p4 renamed them u-boot.img x-loader.img and recovery.img and flashed them just like that in fastboot and fixed my security error/boot loop problem.

    Sent from my LG-P769 using xda app-developers app
    View
    1
    L
    Lelus
    byt3b0mb said:
    i do thank you for the file. is b u-boot?

    would you be able to lend a hand as to how to go about flashing these? I can use omap to get to fastboot but i cant seem to get these to flash
    Click to expand...
    Click to collapse
    fastboot flash u-boot b.bin
    View

New posts