Hello everyone!
I'd like to better understand my smartphone's Partitions Layout...
At the moment I'm inside TWRP and I managed to enter into Shell as root:
Code:
\platform-tools>adb.exe shell
~ #
So... I'm gathering these infos:
~ # fdisk /dev/block/mmcblk0
Code:
Found valid GPT with protective MBR; using GPT
Command (m for help): p
Disk /dev/block/mmcblk0: 30535680 sectors, 2622M
Logical sector size: 512
Disk identifier (GUID): 98101b32-bbe2-4bf2-a06e-2bb33d000c20
Partition table holds up to 52 entries
First usable sector is 34, last usable sector is 30535646
Number Start (sector) End (sector) Size Code Name
1 131072 303103 84.0M 0700 modem
2 393216 393217 1024 0700 fsc
3 393218 393233 8192 0700 ssd
4 393234 394257 512K 0700 sbl1
5 394258 395281 512K 0700 sbl1bak
6 395282 396305 512K 0700 rpm
7 396306 397329 512K 0700 rpmbak
8 397330 401425 2048K 0700 tz
9 401426 405521 2048K 0700 tzbak
10 405522 406033 256K 0700 devcfg
11 406034 406545 256K 0700 devcfgbak
12 406546 439313 16.0M 0700 dsp
13 439314 442385 1536K 0700 modemst1
14 442386 445457 1536K 0700 modemst2
15 524288 524351 32768 0700 DDR
16 524352 527423 1536K 0700 fsg
17 527424 527455 16384 0700 sec
18 655360 677887 11.0M 0700 splash
19 786432 788479 1024K 0700 aboot
20 788480 790527 1024K 0700 abootbak
21 790528 921599 64.0M 0700 boot
22 921600 1052671 64.0M 0700 recovery
23 1052672 1054719 1024K 0700 devinfo
24 1054720 7346175 3072M 0700 system
25 7471104 7995391 256M 0700 cache
26 7995392 8060927 32.0M 0700 persist
27 8060928 8062975 1024K 0700 misc
28 8062976 8063999 512K 0700 keystore
29 8064000 8064063 32768 0700 config
30 8064064 8588351 256M 0700 oem
31 8650752 8650815 32768 0700 limits
32 8781824 8782847 512K 0700 mota
33 8782848 8784895 1024K 0700 dip
34 8784896 8850431 32.0M 0700 mdtp
35 8850432 8851455 512K 0700 syscfg
36 8851456 8859647 4096K 0700 mcfg
37 8912896 8913151 128K 0700 lksecapp
38 8913152 8913407 128K 0700 lksecappbak
39 8913408 8913919 256K 0700 cmnlib
40 8913920 8914431 256K 0700 cmnlibbak
41 8914432 8914943 256K 0700 cmnlib64
42 8914944 8915455 256K 0700 cmnlib64bak
43 8915456 8915967 256K 0700 keymaster
44 8915968 8916479 256K 0700 keymasterbak
45 9043968 9044479 256K 0700 apdp
46 9044480 9044991 256K 0700 msadp
47 9044992 9045007 8192 0700 dpo
48 9045008 9176079 64.0M 0700 logdump
49 9176080 30535646 10.1G 0700 userdata
~ # mount
Code:
rootfs on / type rootfs (rw,seclabel,size=853376k,nr_inodes=134849)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=936796k,nr_inodes=138672,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime,gid=3009,hidepid=2)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime,size=936796k,nr_inodes=138672)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
/dev/block/mmcblk0p25 on /cache type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk1p1 on /external_sd type vfat (rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/block/mmcblk0p24 on /system type ext4 (rw,seclabel,relatime,data=ordered)
~ # ls -lh /dev/block/platform/soc/7824900.sdhci/ | sort -g
Code:
drwxr-xr-x 2 root root 1020 Feb 17 19:54 by-name
drwxr-xr-x 2 root root 1020 Feb 17 19:54 by-num
lrwxrwxrwx 1 root root 18 Feb 17 19:54 mmcblk0 -> /dev/block/mmcblk0
lrwxrwxrwx 1 root root 20 Feb 17 19:54 mmcblk0p1 -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 Feb 17 19:54 mmcblk0p2 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 Feb 17 19:54 mmcblk0p3 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 Feb 17 19:54 mmcblk0p4 -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 Feb 17 19:54 mmcblk0p5 -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 Feb 17 19:54 mmcblk0p6 -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 Feb 17 19:54 mmcblk0p7 -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 Feb 17 19:54 mmcblk0p8 -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 Feb 17 19:54 mmcblk0p9 -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p10 -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p11 -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p12 -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p13 -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p14 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p15 -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p16 -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p17 -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p18 -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p19 -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p20 -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p21 -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p22 -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p23 -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p24 -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p25 -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p26 -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p27 -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p28 -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p29 -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p30 -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p31 -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p32 -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p33 -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p34 -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p35 -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p36 -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p37 -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p38 -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p39 -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p40 -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p41 -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p42 -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p43 -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p44 -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p45 -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p46 -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p47 -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p48 -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p49 -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 22 Feb 17 19:54 mmcblk0rpmb -> /dev/block/mmcblk0rpmb
~ # ls -lh /dev/block/platform/soc/7824900.sdhci/by-name | sort -f -k6
Code:
lrwxrwxrwx 1 root root 21 Feb 17 19:54 aboot -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 Feb 17 19:54 abootbak -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 Feb 17 19:54 apdp -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 21 Feb 17 19:54 boot -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 Feb 17 19:54 cache -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 Feb 17 19:54 cmnlib -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 Feb 17 19:54 cmnlib64 -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 Feb 17 19:54 cmnlib64bak -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 Feb 17 19:54 cmnlibbak -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 Feb 17 19:54 config -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 Feb 17 19:54 DDR -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 Feb 17 19:54 devcfg -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Feb 17 19:54 devcfgbak -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 Feb 17 19:54 devinfo -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 Feb 17 19:54 dip -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 Feb 17 19:54 dpo -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 Feb 17 19:54 dsp -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 Feb 17 19:54 fsc -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 Feb 17 19:54 fsg -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 Feb 17 19:54 keymaster -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 Feb 17 19:54 keymasterbak -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 Feb 17 19:54 keystore -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 Feb 17 19:54 limits -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 Feb 17 19:54 lksecapp -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 21 Feb 17 19:54 lksecappbak -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 Feb 17 19:54 logdump -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mcfg -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mdtp -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 Feb 17 19:54 misc -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 20 Feb 17 19:54 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 Feb 17 19:54 modemst1 -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 Feb 17 19:54 modemst2 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mota -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 Feb 17 19:54 msadp -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 Feb 17 19:54 oem -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 Feb 17 19:54 persist -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 Feb 17 19:54 recovery -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 20 Feb 17 19:54 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 Feb 17 19:54 rpmbak -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 Feb 17 19:54 sbl1 -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 Feb 17 19:54 sbl1bak -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 Feb 17 19:54 sec -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 Feb 17 19:54 splash -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 20 Feb 17 19:54 ssd -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 Feb 17 19:54 syscfg -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 Feb 17 19:54 system -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 20 Feb 17 19:54 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 Feb 17 19:54 tzbak -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 Feb 17 19:54 userdata -> /dev/block/mmcblk0p49
~ # find / -iname "*fstab*"
Code:
/cache/recovery/recovery.fstab
/cache/recovery/storage.fstab
/system/etc/vold.fstab
/system/vendor/etc/fstab.qcom
find: /sys/kernel/slab/L2TP/IPv6: No such file or directory
find: /sys/kernel/slab/L2TP/IP: No such file or directory
/etc/fstab
/etc/twrp.fstab
Contents of ~ # find / -iname "*fstab*"
Code:
/cache/recovery/recovery.fstab
### EMPTY FILE ###
\\\
/cache/recovery/storage.fstab
/data/media;Internal Storage;
/external_sd;External SD;
/usb-otg;USB OTG;
\\\
/system/etc/vold.fstab
# Copyright (c) 2013, The Linux Foundation. All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions are
# met:
# * Redistributions of source code must retain the above copyright
# notice, this list of conditions and the following disclaimer.
# * Redistributions in binary form must reproduce the above
# copyright notice, this list of conditions and the following
# disclaimer in the documentation and/or other materials provided
# with the distribution.
# * Neither the name of The Linux Foundation nor the names of its
# contributors may be used to endorse or promote products derived
# from this software without specific prior written permission.
#
# THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT
# ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS
# BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
# CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
# SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
# BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
# OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN
# IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
dev_mount sdcard /storage/sdcard1 auto /devices/msm_sdcc.2/mmc_host
# MTP
#dev_mount sdcard2 /mnt/sdcard/external_sd auto /devices/platform/msm_sdcc.3/mmc_host
\\\
/system/vendor/etc/fstab.qcom
# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
#TODO: Add 'check' as fs_mgr_flags with data partition.
# Currently we dont have e2fsck compiled. So fs check would failed.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
#/dev/block/bootdevice/by-name/system /system ext4 ro,barrier=1,discard wait, verify
/dev/block/bootdevice/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=1,noauto_da_alloc,discard wait,resize,forceencrypt=footer,quota
/devices/platform/soc/7864900.sdhci/mmc_host* /storage/sdcard1 vfat nosuid,nodev wait,voldmanaged=sdcard1:auto,noemulatedsd,encryptable=footer
/devices/soc/7864900.sdhci/mmc_host* /storage/sdcard1 vfat nosuid,nodev wait,voldmanaged=sdcard1:auto,noemulatedsd,encryptable=footer
/devices/platform/soc/78db000.usb/msm_hsusb_host* /storage/usbotg vfat nosuid,nodev wait,voldmanaged=usbotg:auto
/devices/soc/78db000.usb/msm_hsusb_host* /storage/usbotg vfat nosuid,nodev wait,voldmanaged=usbotg:auto
/dev/block/bootdevice/by-name/config /frp emmc defaults defaults
/dev/block/bootdevice/by-name/misc /misc emmc defaults defaults
/dev/block/bootdevice/by-name/cache /cache ext4 noatime,nosuid,nodev,barrier=1 wait
/dev/block/bootdevice/by-name/modem /firmware vfat ro,shortname=lower,uid=1000,gid=1000,dmask=227,fmask=337,context=u:object_r:firmware_file:s0 wait
/dev/block/bootdevice/by-name/dsp /dsp ext4 ro,nosuid,nodev,barrier=1 wait
\\\
/etc/fstab
/dev/block/mmcblk0p25 /cache ext4 rw 0 0
/dev/block/mmcblk0p24 /system ext4 rw 0 0
/dev/block/dm-0 /data ext4 rw 0 0
/dev/block/mmcblk1p1 /external_sd vfat rw 0 0
/usb-otg vfat rw 0 0
\\\
/etc/twrp.fstab
/cache ext4 /dev/block/bootdevice/by-name/cache
/system ext4 /dev/block/bootdevice/by-name/system
/system_image emmc /dev/block/bootdevice/by-name/system
/data ext4 /dev/block/bootdevice/by-name/userdata flags=encryptable=footer;length=-16384
/boot emmc /dev/block/bootdevice/by-name/boot
/recovery emmc /dev/block/bootdevice/by-name/recovery
/misc emmc /dev/block/bootdevice/by-name/misc
/external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="External SD";storage;wipeingui;removable
/usb-otg vfat /dev/block/sda1 /dev/block/sda flags=display="USB OTG";storage;wipeingui;removable
And now... Questions time!
Which fstab should I trust? Why there are so many different ones?
Why my smartphone has the by-name/ directory inside this path: /dev/block/platform/soc/7824900.sdhci/ ?
In case I would use ddto backup or restore or reflash partitions, can i use dd within ADB Shell while I'm into Recovery (TWRP)?
Will dd be capable of reflashing .bin and .img and .mbn partitions even if I am OEM locked-out from Fastboot?
Why I cannot mount /datawhile inside TWRP?
Code:
~ # mount -o noatime,nosuid,nodev,barrier=1,noauto_da_alloc,discard,wait,resize,forceencrypt=footer,quota /dev/block/bootdevice/by-name/userdata /data \\\ mount: mounting /dev/block/bootdevice/by-name/userdata on /data failed: Device or resource busy
Many thanks guys!!
1. vold fstab is for external storage managed by StorageManagerService in android mode.
vendor/etc fstab is fstab for emmc storage provided by vendor. other fstabs are generated by and only used by TWRP.
2. android partitions are always referenced by it's symlinks generated from kernel. for example on A/B devices the /dev/block/bootdevice/by-name/system is linked to either /dev/block/bootdevice/by-name/system_a or /dev/block/bootdevice/by-name/system_b depending on active slot. in android mode you will see /dev/block/dm-0 instead as the partition is protected by dm-verity.
3. we don't care about real block partition, you can just dd its symlink. (Note, it requires exFAT MicroSD Card, FAT32 has 4 GB file size limit.) it's even more comfortable to just adb pull partition btw.
4. /data is already mounted in TWRP (Device or resource busy) except for failed decrypts (check /tmp/recovery.log)
if /dev/block/bootdevice/by-name/userdata is decrypted successfully, a new (decrypted) block device /dev/block/dm-0 is created by dm-crypt and mounted to /data.
/proc/partitions is maintained in realtime by kernel.
aIecxs said:
4. /data is already mounted in TWRP (Device or resource busy) except for failed decrypts (check /tmp/recovery.log)
if /dev/block/bootdevice/by-name/userdata is decrypted successfully, a new (decrypted) block device /dev/block/dm-0 is created by dm-crypt and mounted to /data.
/proc/partitions is maintained in realtime by kernel.
Click to expand...
Click to collapse
Hey... I'm doing some testing... Here's the steps I've done so far:
wipe / reformat all partitions
entirely re-flash the whole Stock ROM
reboot
completed the Startup Wizard
set a PIN when requested (instead of a Password or a Pattern)
boot into Android
reboot
boot again into Android
reboot to Bootloader
Bash:
fastboot flash recovery twrp.img
reboot into Android
reboot into TWRP
[V] Never show this screen during boot again
Swipe to Allow Modifications
TWRP is NOT asking me the PIN to decrypt /data
/data is NOT mounted, but with different error now (see logs down below)
every time I boot into TWRP, it always keeps me asking Swipe to Allow Modifications!!!
recovery.log
Bash:
[...]
Data successfully decrypted, new block device: '/dev/block/dm-0'
I:Unable to mount '/data'
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
Updating partition details...
I:Unable to mount '/data'
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
...done
I:Unable to mount '/data'
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
Unable to mount storage
/data | /dev/block/dm-0 | Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent Can_Be_Encrypted Is_Encrypted Is_Decrypted Has_Data_Media Can_Encrypt_Backup Use_Userdata_Encryption Is_Storage Is_Settings_Storage
Symlink_Path: /data/media
Symlink_Mount_Point: /sdcard
Primary_Block_Device: /dev/block/mmcblk0p49
Decrypted_Block_Device: /dev/block/dm-0
Crypto_Key_Location: footer
Length: -16384
Display_Name: data
Storage_Name: Internal Storage
Backup_Path: /data
Backup_Name: data
Backup_Display_Name: Data
Storage_Path: /data/media
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files
MTP_Storage_ID: 65537
I:Unmounting main partitions...
Successfully decrypted with default password.
I:Unable to mount '/data'
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
Updating partition details...
I:Unable to mount '/data'
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
...done
I:Unable to mount '/data'
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
Unable to mount storage
I:Unmounting main partitions...
[...]
I:Unable to mount '/data'
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
I:Unable to mount '/data'
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
I:Unable to mount '/data'
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
I:Unable to mount '/data'
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
I:Unable to mount '/data'
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
I:Unable to mount '/data'
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
Failed to mount '/data' (No such process)
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
I:Unable to mount /data/media during GUI startup.
[...]
I:Unable to mount '/data'
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
I:Copying file /cache/recovery/log to /cache/recovery/last_log
I:Unable to mount '/data'
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
I:Unable to mount '/data'
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
Unable to mount /data/media/TWRP/.twrps
I:Attempt to load settings from settings file...
I:InfoManager file '/data/media/TWRP/.twrps' not found.
I:Backup folder set to '/data/media/TWRP/BACKUPS/WF012646'
I:Copying file /etc/recovery.fstab to /cache/recovery/recovery.fstab
I:Version number saved to '/cache/recovery/.version'
I:Unable to mount '/data'
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:TWFunc::Set_Brightness: Setting brightness control to 128
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/en.xml' directly
parsing languageFile
parsing languageFile done
I:Translating partition display names
[...]
Failed to mount '/data' (No such process)
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
I:TWFunc::Set_Brightness: Setting brightness control to 5
I:TWFunc::Set_Brightness: Setting brightness control to 0
~ # dmesg
Bash:
[...]
[ 5.628850] SELinux: initialized (dev mmcblk0p25, type ext4), uses xattr
[ 5.658433] EXT4-fs (mmcblk0p49): VFS: Can't find ext4 filesystem
[ 5.658777] EXT4-fs (mmcblk0p49): VFS: Can't find ext4 filesystem
[ 5.667880] EXT4-fs (mmcblk0p49): VFS: Can't find ext4 filesystem
[ 5.668184] EXT4-fs (mmcblk0p49): VFS: Can't find ext4 filesystem
[...]
[ 8.417484] device-mapper: req-crypt: req_crypt_ctr: Mapping block_device /dev/block/mmcblk0p49 to dm-req-crypt ok!
[...]
[ 14.258270] EXT4-fs (dm-0): warning: maximal mount count reached, running e2fsck is recommended
[ 14.259729] EXT4-fs warning (device dm-0): ext4_enable_quotas:5282: Failed to enable quota tracking (type=0, err=-3). Please run e2fsck to fix.
[ 14.259840] EXT4-fs (dm-0): mount failed
[ 14.261825] EXT4-fs (dm-0): warning: maximal mount count reached, running e2fsck is recommended
[ 14.263192] EXT4-fs warning (device dm-0): ext4_enable_quotas:5282: Failed to enable quota tracking (type=0, err=-3). Please run e2fsck to fix.
[ 14.263286] EXT4-fs (dm-0): mount failed
[...]
[ 56.822575] EXT4-fs (dm-0): warning: maximal mount count reached, running e2fsck is recommended
[ 56.824051] EXT4-fs warning (device dm-0): ext4_enable_quotas:5282: Failed to enable quota tracking (type=0, err=-3). Please run e2fsck to fix.
[ 56.824153] EXT4-fs (dm-0): mount failed
[ 56.826017] EXT4-fs (dm-0): warning: maximal mount count reached, running e2fsck is recommended
[ 56.827383] EXT4-fs warning (device dm-0): ext4_enable_quotas:5282: Failed to enable quota tracking (type=0, err=-3). Please run e2fsck to fix.
[ 56.827477] EXT4-fs (dm-0): mount failed
[...]
~ # e2fsck /dev/block/dm-0
Bash:
e2fsck 1.42.9 (28-Dec-2013)
/dev/block/dm-0 has unsupported feature(s): quota
e2fsck: Get a newer version of e2fsck!
No such process is known issue with disk quota. try to mount dm-0 read-only with ro,noexec,noload,noatime flags.
(Unrelated) for changing default_password try this app (may be outdated)
Cryptfs Password - Apps on Google Play
Easily set a complex disk encryption password different from the lockscreen one
play.google.com
aIecxs said:
try to mount dm-0 read-only with ro,noexec,noload,noatime flags.
Click to expand...
Click to collapse
Code:
~ # mount -o ro,noexec,noload,noatime /dev/block/dm-0
~ # mount | grep dm-0
/dev/block/dm-0 on /data type ext4 (ro,seclabel,noexec,noatime,norecovery)
And what if I completely disable /data encryption? Is it a viable option?
Are there some infos on how to disable Android encrypting /data? Can Stock ROMs be patched to disable encryption?
disable avb/dm-verity to allow modification on /system.
in vendor/etc fstab replace forceencrypt= flag with encryptable= and format userdata partition.
there exist flashable zip for this
no-verity-opt-encrypt.zip
(recommended for FDE)
Disable_Dm-Verity_ForceEncrypt.zip
(can also remove disk quota, read instructions)
Related
Hi,
Can anyone please tell me how I may check the mount point mappings for my phone?
All i can understand is /system is /dev/block/mmcblk0p3"
but how do check for the rest?
I already tried the following commands in terminal emulator but they didn't help:
mount
/proc/partitions
How did those commands not help? What was their output?
Maybe try
cat/proc/partitions
Or
ls -l /dev/block
Or
df
busybox df -hm
Also try with superuser permission, normally I do this in adb shell but terminal should work just fine
Sent from my Nexus 4 using xda premium
ibshar said:
Hi,
Can anyone please tell me how I may check the mount point mappings for my phone?
All i can understand is /system is /dev/block/mmcblk0p3"
but how do check for the rest?
I already tried the following commands in terminal emulator but they didn't help:
mount
/proc/partitions
Click to expand...
Click to collapse
To find out the rest of the mount points and block partition layouts from either terminal or adb shell run the following commands (Make sure to run the commands as root):
First:
Code:
cd /dev/block/platform
Next type:
Code:
ls
And you should see a platform name for example on my Nexus 10 it's dw_mmc.0 cd into the platform name directory (For example):
Code:
cd dw_mmc.0
Then after you have done that cd into the by-name directory:
Code:
cd by-name
And finally once in the by-name directory run the command:
Code:
ls -l
Which should produce an output similar to the following giving you a complete list of mount points and partition block layout:
Code:
lrwxrwxrwx root root 2013-07-25 12:35 boot -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-07-25 12:35 cache -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-07-25 12:35 efs -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-07-25 12:35 metadata -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-07-25 12:35 misc -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2013-07-25 12:35 param -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-07-25 12:35 recovery -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-07-25 12:35 system -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-07-25 12:35 userdata -> /dev/block/mmcblk0p9
Let me know if you still have questions .
@demkantor: This is the output i get for all those commands:
Code:
[email protected]:/ $ su
su
[email protected]:/ # mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/[email protected] /system ext4 ro,relatime,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected]_ro /system/secro ext4 rw,nosuid,nodev,relatime,data=ordered 0 0
/[email protected] /data ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/[email protected] /cache ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/vold/179:97 /storage/sdcard0 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
/dev/block/vold/179:97 /mnt/secure/asec 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
tmpfs /storage/sdcard0/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/vold/179:6 /storage/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0
702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
[email protected]:/ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 3763200 mmcblk0
179 1 1 mmcblk0p1
179 2 5120 mmcblk0p2
179 3 524288 mmcblk0p3
179 4 524288 mmcblk0p4
179 5 2621440 mmcblk0p5
179 6 56416 mmcblk0p6
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
179 96 30760960 mmcblk1
179 97 30756864 mmcblk1p1
[email protected]:/ # ls -l /dev/block
ls -l /dev/block
brw------- root root 7, 0 2013-07-25 10:36 loop0
brw------- root root 7, 1 2013-07-25 10:36 loop1
brw------- root root 7, 2 2013-07-25 10:36 loop2
brw------- root root 7, 3 2013-07-25 10:36 loop3
brw------- root root 7, 4 2013-07-25 10:36 loop4
brw------- root root 7, 5 2013-07-25 10:36 loop5
brw------- root root 7, 6 2013-07-25 10:36 loop6
brw------- root root 7, 7 2013-07-25 10:36 loop7
brw-rw---- root system 179, 0 2013-07-25 10:36 mmcblk0
brw------- root root 179, 32 2013-07-25 10:36 mmcblk0boot0
brw------- root root 179, 64 2013-07-25 10:36 mmcblk0boot1
brw------- root root 179, 1 2013-07-25 10:36 mmcblk0p1
brw------- root root 179, 2 2013-07-25 10:36 mmcblk0p2
brw------- root root 179, 3 2013-07-25 10:36 mmcblk0p3
brw------- root root 179, 4 2013-07-25 10:36 mmcblk0p4
brw------- root root 179, 5 2013-07-25 10:36 mmcblk0p5
brw------- root root 179, 6 2013-07-25 10:36 mmcblk0p6
brw------- root root 179, 96 2013-07-25 10:36 mmcblk1
brw------- root root 179, 97 2013-07-25 10:36 mmcblk1p1
drwxr-xr-x root root 2013-07-25 10:36 platform
drwx------ root root 2013-07-25 10:36 vold
[email protected]:/ # df
df
Filesystem Size Used Free Blksize
/dev 236M 56K 236M 4096
/mnt/asec 236M 0K 236M 4096
/mnt/obb 236M 0K 236M 4096
/system 504M 330M 173M 4096
/system/secro 4M 4M 0K 4096
/data 2G 940M 1G 4096
/cache 504M 9M 494M 4096
/storage/sdcard0 29G 12G 16G 32768
/mnt/secure/asec 29G 12G 16G 32768
/storage/sdcard1 55M 24K 54M 4096
[email protected]:/ # busybox df -hm
busybox df -hm
Filesystem Size Used Available Use% Mounted on
tmpfs 236.8M 56.0K 236.7M 0% /dev
tmpfs 236.8M 0 236.8M 0% /mnt/asec
tmpfs 236.8M 0 236.8M 0% /mnt/obb
/[email protected] 504.4M 330.9M 173.5M 66% /system
/[email protected]_ro 4.9M 4.9M 0 100% /system/secro
/[email protected] 2.5G 940.0M 1.5G 37% /data
/[email protected] 504.4M 9.6M 494.8M 2% /cache
/dev/block/vold/179:97
29.3G 12.8G 16.5G 44% /storage/sdcard0
/dev/block/vold/179:97
29.3G 12.8G 16.5G 44% /mnt/secure/asec
/dev/block/vold/179:6
55.0M 24.0K 55.0M 0% /storage/sdcard1
[email protected]:/ #
As you can see no mapping shown..
@shimp208: I tried that and this is what i got as output:
Code:
[email protected]:/dev/block/platform # ls
ls
mtk-sd.0
mtk-sd.1
[email protected]:/dev/block/platform # ls -l
ls -l
drwxr-xr-x root root 2013-07-25 10:36 mtk-sd.0
drwxr-xr-x root root 2013-07-25 10:36 mtk-sd.1
[email protected]:/dev/block/platform # ls -l mtk-sd.0
ls -l mtk-sd.0
drwxr-xr-x root root 2013-07-25 10:36 by-num
lrwxrwxrwx root root 2013-07-25 10:36 mmcblk0 -> /dev/block/mmcblk0
lrwxrwxrwx root root 2013-07-25 10:36 mmcblk0boot0 -> /dev/block/mmcblk0boot0
lrwxrwxrwx root root 2013-07-25 10:36 mmcblk0boot1 -> /dev/block/mmcblk0boot1
lrwxrwxrwx root root 2013-07-25 10:36 mmcblk0p1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-07-25 10:36 mmcblk0p2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-07-25 10:36 mmcblk0p3 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-07-25 10:36 mmcblk0p4 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-07-25 10:36 mmcblk0p5 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-07-25 10:36 mmcblk0p6 -> /dev/block/mmcblk0p6
[email protected]:/dev/block/platform # ls -l mtk-sd.1
ls -l mtk-sd.1
drwxr-xr-x root root 2013-07-25 10:36 by-num
lrwxrwxrwx root root 2013-07-25 10:36 mmcblk1 -> /dev/block/mmcblk1
lrwxrwxrwx root root 2013-07-25 10:36 mmcblk1p1 -> /dev/block/mmcblk1p1
So as you can see, still not showing the directory name mapping, like which one is system and which one is data etc..
Instead of mapping the mount point directory with dev block it shows some
/[email protected]
/[email protected]_ro
/[email protected]
/[email protected]
This time i ran those commands with ADB..
ibshar said:
So as you can see, still not showing the directory name mapping, like which one is system and which one is data etc..
Instead of mapping the mount point directory with dev block it shows some
/[email protected]
/[email protected]_ro
/[email protected]
/[email protected]
This time i ran those commands with ADB..
Click to expand...
Click to collapse
Try running these commands to get the output:
Code:
ls - l /dev/block/platform/mtk-sd.0/by-name
Or cd into the mtk-sd.0 then:
Code:
ls -l
I think you meant cd into by-num folder, coz there is no folder named by-name. So here is the output:
Code:
[email protected]:/dev/block/platform/mtk-sd.0/by-num $ ls -l
ls -l
lrwxrwxrwx root root 2013-07-25 10:36 p1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-07-25 10:36 p2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-07-25 10:36 p3 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-07-25 10:36 p4 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-07-25 10:36 p5 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-07-25 10:36 p6 -> /dev/block/mmcblk0p6
ok, i think i found most of it, listing the files in root directory showed that they have made some symlinks and that actually maps up with teh mount command output.
ls -l /
Code:
[email protected] -> /dev/block/mmcblk0p3
[email protected] -> /dev/block/mmcblk0p4
[email protected] -> /dev/block/mmcblk0p1
[email protected] -> /dev/block/mmcblk0p6
[email protected]_ro -> /dev/block/mmcblk0p2
[email protected] -> /dev/block/mmcblk0p5
etc -> /system/etc
thus mapping it with the output of mount command gives:
Code:
em[email protected] -> /dev/block/mmcblk0p3 -> /system
[email protected] -> /dev/block/mmcblk0p4 -> /cache
[email protected] -> /dev/block/mmcblk0p1 ->
[email protected] -> /dev/block/mmcblk0p6
[email protected]_ro -> /dev/block/mmcblk0p2 -> /system/secro
[email protected] -> /dev/block/mmcblk0p5 -> /data
So now i know about the system, data and cache partitions mapping.. Just need to know about the boot and recovery mapping, also how to get the ramdisk image?
ibshar said:
ok, i think i found most of it, listing the files in root directory showed that they have made some symlinks and that actually maps up with teh mount command output.
ls -l /
Code:
[email protected] -> /dev/block/mmcblk0p3
[email protected] -> /dev/block/mmcblk0p4
[email protected] -> /dev/block/mmcblk0p1
[email protected] -> /dev/block/mmcblk0p6
[email protected]_ro -> /dev/block/mmcblk0p2
[email protected] -> /dev/block/mmcblk0p5
etc -> /system/etc
thus mapping it with the output of mount command gives:
Code:
[email protected] -> /dev/block/mmcblk0p3 -> /system
[email protected] -> /dev/block/mmcblk0p4 -> /cache
[email protected] -> /dev/block/mmcblk0p1 ->
[email protected] -> /dev/block/mmcblk0p6
[email protected]_ro -> /dev/block/mmcblk0p2 -> /system/secro
[email protected] -> /dev/block/mmcblk0p5 -> /data
So now i know about the system, data and cache partitions mapping.. Just need to know about the boot and recovery mapping, also how to get the ramdisk image?
Click to expand...
Click to collapse
From looking at your devices partition layout from what I can tell I'm guessing mmcblk0boot0 and mmcblk0boot1 are the boot partition blocks and that mmcblk0p2 is your recovery partition if you post the images for those files I can take a look at them for you if you would like to better determine which one truly boot and which is one is truly recovery. Also you can get the ramdisk by extracting it from the boot.img file using a tool such as this one.
shimp208 said:
From looking at your devices partition layout from what I can tell I'm guessing mmcblk0boot0 and mmcblk0boot1 are the boot partition blocks and that mmcblk0p2 is your recovery partition if you post the images for those files I can take a look at them for you if you would like to better determine which one truly boot and which is one is truly recovery. Also you can get the ramdisk by extracting it from the boot.img file using a tool such as this one.
Click to expand...
Click to collapse
Hi thanks for the help.. I have extracted those partitions and uploaded them, please have a look and let me know if they are correct.. http://d-h.st/24I
ibshar said:
Hi thanks for the help.. I have extracted those partitions and uploaded them, please have a look and let me know if they are correct.. http://d-h.st/24I
Click to expand...
Click to collapse
After taking a look at the partition images it seems that your device is using an unconventional partition setup as I was not able to successfully unpack any of the images. Judging from the size of the partitions however the boot partitions you provided do seem to be boot partitions and the recovery partition does seem to be the recovery partition. Unfortunately I can't verify this further unfortunately because of the unconventional partition layout.
shimp208 said:
After taking a look at the partition images it seems that your device is using an unconventional partition setup as I was not able to successfully unpack any of the images. Judging from the size of the partitions however the boot partitions you provided do seem to be boot partitions and the recovery partition does seem to be the recovery partition. Unfortunately I can't verify this further unfortunately because of the unconventional partition layout.
Click to expand...
Click to collapse
Never mind, thanks for the help..
need mount point to setup kitchen.
@ibshar
Sir can you please tell me the mount point for Micromax A110. i want to setup android kitchen.
if possible can you upload the file need to placed in the edify_defs folder of the android kitchen.
Thanks in advance...
subhashdas said:
@ibshar
Sir can you please tell me the mount point for Micromax A110. i want to setup android kitchen.
if possible can you upload the file need to placed in the edify_defs folder of the android kitchen.
Thanks in advance...
Click to expand...
Click to collapse
Sorry man but I don't use that file in the kitchen. I just edit the mount points manually.. The main partitions are
mount("ext4", "EMMC", "/dev/block/mmcblk0p3", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p5", "/data");
mount("ext4", "EMMC", "/dev/block/mmcblk0p7", "/cache");
shimp208 said:
To find out the rest of the mount points and block partition layouts from either terminal or adb shell run the following commands (Make sure to run the commands as root):
First:
Code:
cd /dev/block/platform
Next type:
Code:
ls
And you should see a platform name for example on my Nexus 10 it's dw_mmc.0 cd into the platform name directory (For example):
Code:
cd dw_mmc.0
Then after you have done that cd into the by-name directory:
Code:
cd by-name
And finally once in the by-name directory run the command:
Code:
ls -l
Which should produce an output similar to the following giving you a complete list of mount points and partition block layout:
Code:
lrwxrwxrwx root root 2013-07-25 12:35 boot -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-07-25 12:35 cache -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-07-25 12:35 efs -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-07-25 12:35 metadata -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-07-25 12:35 misc -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2013-07-25 12:35 param -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-07-25 12:35 recovery -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-07-25 12:35 system -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-07-25 12:35 userdata -> /dev/block/mmcblk0p9
Let me know if you still have questions .
Click to expand...
Click to collapse
WHAT THE F*** DUDE!!! After searching all over the Internet, Google, XDA for almost a day... I've finally found the answer to my question!!!
Hi All!!
I have a Qmoible A5Classic and I want to develop its CWM Recovery. I want to fetch its recovery by
Code:
dd if=etc of=abc
but the problem is i cannot find which partition is my recovery partition.
Code:
cat proc/partitions
shows:
Code:
major minor #blocks name
7 0 1254 loop0
179 0 3815552 mmcblk0
179 1 1 mmcblk0p1
179 2 163840 mmcblk0p2
179 3 1064960 mmcblk0p3
179 4 2028784 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 524288 mmcblk0p6
179 16 2048 mmcblk0boot1
179 8 2048 mmcblk0boot0
179 24 1949696 mmcblk1
179 25 1948672 mmcblk1p1
and
Code:
cat proc/mounts
show these:
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
[email protected] /system ext4 rw,relatime,user_xattr,commit=1,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/loop0 /mnt/cd-rom iso9660 ro,relatime 0 0
[email protected] /data ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
[email protected] /cache ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/vold/179:4 /mnt/sdcard2 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
/dev/block/vold/179:25 /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
/dev/block/vold/179:25 /mnt/secure/asec 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
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
Can anyone please point out the right partition?
PS: It is rooted.
Regards
ssm14293 said:
Hi All!!
Can anyone please point out the right partition?
PS: It is rooted.
Regards
Click to expand...
Click to collapse
I would recommend running the following command as root from terminal emulator:
Code:
cat /cache/recovery/last_log
This should tell you which partition is your recovery partition that you can then dump a copy of the stock recovery.img to your device. Let me know if you still have questions.
Sent from my SCH-I535 using xda premium
cmd says /recovery emmc recovery (null) 0
shimp208 said:
I would recommend running the following command as root from terminal emulator:
Code:
cat /cache/recovery/last_log
This should tell you which partition is your recovery partition that you can then dump a copy of the stock recovery.img to your device. Let me know if you still have questions.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
This is what I get upon running your command:
Code:
Partition Information:
preloader 0x0000000000040000 0x0000000000000000 2 /dev/misc-sd
dsp_bl 0x00000000005c0000 0x0000000000040000 2 /dev/misc-sd
mbr 0x0000000000004000 0x0000000000000000 2 /dev/block/mmcblk0
ebr1 0x000000000005c000 0x0000000000004000 2 /dev/block/mmcblk0p1
pmt 0x0000000000400000 0x0000000000060000 2 /dev/block/mmcblk0
nvram 0x0000000000300000 0x0000000000460000 2 /dev/block/mmcblk0
seccfg 0x0000000000020000 0x0000000000760000 2 /dev/block/mmcblk0
uboot 0x0000000000060000 0x0000000000780000 2 /dev/block/mmcblk0
bootimg 0x0000000000600000 0x00000000007e0000 2 /dev/block/mmcblk0
recovery 0x0000000000600000 0x0000000000de0000 2 /dev/block/mmcblk0
sec_ro 0x0000000000600000 0x00000000013e0000 2 /dev/block/mmcblk0p5
misc 0x0000000000060000 0x00000000019e0000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000001a40000 2 /dev/block/mmcblk0
expdb 0x00000000000a0000 0x0000000001d40000 2 /dev/block/mmcblk0
ebr2 0x0000000000004000 0x0000000001de0000 2 /dev/block/mmcblk0
android 0x0000000020100000 0x0000000001de4000 2 /dev/block/mmcblk0p6
cache 0x000000000a100000 0x0000000021ee4000 2 /dev/block/mmcblk0p2
usrdata 0x0000000041100000 0x000000002bfe4000 2 /dev/block/mmcblk0p3
fat 0x0000000000000001 0x000000006d0e4000 2 /dev/block/mmcblk0p4
bmtpool 0x000000007bafbfff 0xffffffffffa00000 2 /dev/block/mmcblk0
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc boot (null) 0
2 /cache ext4 /dev/block/mmcblk0p2 (null) 0
3 /data ext4 /dev/block/mmcblk0p3 (null) 0
4 /misc emmc misc (null) 0
5 /recovery emmc recovery (null) 0
6 /sdcard vfat /dev/block/mmcblk1 /dev/block/mmcblk0p4 0
7 /sdcard2 vfat /dev/block/mmcblk0p4 (null) 0
8 /system ext4 /dev/block/mmcblk0p6 (null) 0
ssm14293 said:
This is what I get upon running your command:
Code:
Partition Information:
preloader 0x0000000000040000 0x0000000000000000 2 /dev/misc-sd
dsp_bl 0x00000000005c0000 0x0000000000040000 2 /dev/misc-sd
mbr 0x0000000000004000 0x0000000000000000 2 /dev/block/mmcblk0
ebr1 0x000000000005c000 0x0000000000004000 2 /dev/block/mmcblk0p1
pmt 0x0000000000400000 0x0000000000060000 2 /dev/block/mmcblk0
nvram 0x0000000000300000 0x0000000000460000 2 /dev/block/mmcblk0
seccfg 0x0000000000020000 0x0000000000760000 2 /dev/block/mmcblk0
uboot 0x0000000000060000 0x0000000000780000 2 /dev/block/mmcblk0
bootimg 0x0000000000600000 0x00000000007e0000 2 /dev/block/mmcblk0
recovery 0x0000000000600000 0x0000000000de0000 2 /dev/block/mmcblk0
sec_ro 0x0000000000600000 0x00000000013e0000 2 /dev/block/mmcblk0p5
misc 0x0000000000060000 0x00000000019e0000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000001a40000 2 /dev/block/mmcblk0
expdb 0x00000000000a0000 0x0000000001d40000 2 /dev/block/mmcblk0
ebr2 0x0000000000004000 0x0000000001de0000 2 /dev/block/mmcblk0
android 0x0000000020100000 0x0000000001de4000 2 /dev/block/mmcblk0p6
cache 0x000000000a100000 0x0000000021ee4000 2 /dev/block/mmcblk0p2
usrdata 0x0000000041100000 0x000000002bfe4000 2 /dev/block/mmcblk0p3
fat 0x0000000000000001 0x000000006d0e4000 2 /dev/block/mmcblk0p4
bmtpool 0x000000007bafbfff 0xffffffffffa00000 2 /dev/block/mmcblk0
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc boot (null) 0
2 /cache ext4 /dev/block/mmcblk0p2 (null) 0
3 /data ext4 /dev/block/mmcblk0p3 (null) 0
4 /misc emmc misc (null) 0
5 /recovery emmc recovery (null) 0
6 /sdcard vfat /dev/block/mmcblk1 /dev/block/mmcblk0p4 0
7 /sdcard2 vfat /dev/block/mmcblk0p4 (null) 0
8 /system ext4 /dev/block/mmcblk0p6 (null) 0
Click to expand...
Click to collapse
Very interesting from looking at your partition layout I can see that that /dev/block/mmcblk0 contains your recovery partition. However it appears /dev/block/mmcblk0 is a combined partition that also contains many critical parts of the phones file system such u-boot, /boot, and other bootloader related components. I would recommend running the following commands as root from either ADB shell:
Code:
cd /dev/block/platform
Then from the platform directory list the contents of the directory with the "ls" command. Once you have done that you should see a platform name (Or multiple platform names) for example on my Verizon Galaxy S3 it shows:
Code:
msm_sdcc.1
msm_sdcc.3
Cd into each of the platform directories (Or if there is only one platform directory "cd" into that) and list the contents of the platform directory using the "ls" command and look to see if it list a directory "by-name". If the platform directory your in contains the "by-name" folder run the following command:
Code:
ls -l /dev/block/platform/{platform directory name here}/by-name
If that command returns an output take note of the the block number that contains the recovery partition.
Another suggestion would be to run the following command to try and isolate the recovery.img from the larger /dev/block/mmcblk0 contents:
Code:
dd if=/dev/block/mmcblk0 of=mnt/sdcard/recovery.img bs=1 skip=6291456 count=8257536
Additionally you could try dumping the whole /dev/block/mmcblk0 partition using the command:
Code:
cat /dev/block/mmcblk0 > /mnt/sdcard/recovery.img
Let me know how the above commands work out for you .
shimp208 said:
[/HIDE]
Very interesting from looking at your partition layout I can see that that /dev/block/mmcblk0 contains your recovery partition. However it appears /dev/block/mmcblk0 is a combined partition that also contains many critical parts of the phones file system such u-boot, /boot, and other bootloader related components. I would recommend running the following commands as root from either ADB shell:
Code:
cd /dev/block/platform
Then from the platform directory list the contents of the directory with the "ls" command. Once you have done that you should see a platform name (Or multiple platform names) for example on my Verizon Galaxy S3 it shows:
Code:
msm_sdcc.1
msm_sdcc.3
Cd into each of the platform directories (Or if there is only one platform directory "cd" into that) and list the contents of the platform directory using the "ls" command and look to see if it list a directory "by-name". If the platform directory your in contains the "by-name" folder run the following command:
Code:
ls -l /dev/block/platform/{platform directory name here}/by-name
If that command returns an output take note of the the block number that contains the recovery partition.
Another suggestion would be to run the following command to try and isolate the recovery.img from the larger /dev/block/mmcblk0 contents:
Code:
dd if=/dev/block/mmcblk0 of=mnt/sdcard/recovery.img bs=1 skip=6291456 count=8257536
Additionally you could try dumping the whole /dev/block/mmcblk0 partition using the command:
Code:
cat /dev/block/mmcblk0 > /mnt/sdcard/recovery.img
Let me know how the above commands work out for you .
Click to expand...
Click to collapse
Jahan panha tussi great ho taufa qabul karo!
Click to expand...
Click to collapse
Translation: Dude!!!! Ur great!! please accept my humble gift :victory:
I dont have a by-name folder but only by-num, which really doesnt help. So now I will try your second method, extracting a part of the main image!! I'll tell you the result!!!
Regards
I did what you asked me to and it gave me a 7.87mb img file, but I cannot extract it using the unpack-mt65xx.pl. Invalid file. Can you please point me in the right direction please.
Regards
ssm14293 said:
I did what you asked me to and it gave me a 7.87mb img file, but I cannot extract it using the unpack-mt65xx.pl. Invalid file. Can you please point me in the right direction please.
Regards
Click to expand...
Click to collapse
In that case I would recommend trying to dump the whole /dev/block/mmcblk0 partition and seeing if you can unpack it then.
Some Luck with it...
shimp208 said:
In that case I would recommend trying to dump the whole /dev/block/mmcblk0 partition and seeing if you can unpack it then.
Click to expand...
Click to collapse
Hi I tried to extract the recovery.img created from your command using unmkboot in my Ubuntu VM. I got two files from it, a zImage file and an initramfs.cpio.gz files with this output:
Code:
unmkbootimg version 1.2 - Mikael Q Kuisma <[email protected]>
File ./images/recovery.img not a plain boot image, seeking for embedded image ... found!
Kernel size 3248084
Kernel address 0x10008000
Ramdisk size 506660
Ramdisk address 0x11000000
Secondary size 0
Secondary address 0x10f00000
Kernel tags address 0x10000100
Flash page size 2048
Board name is "1354555027"
Command line ""
This image is built using standard mkbootimg
Extracting kernel to file zImage ...
Extracting root filesystem to file initramfs.cpio.gz ...
All done.
---------------
To recompile this image, use:
mkbootimg --kernel zImage --ramdisk initramfs.cpio.gz --board '1354555027' -o new_boot.img
---------------
Now what can i do from here. I cannot extract the cpio.gz file, how will I do that.
Thanks for helping out!
I cannot dump the whole mmcblk0 because I dont have a memory card large enough for the dump, which is roughly 4gb.
Regards
Few Questions
shimp208 said:
In that case I would recommend trying to dump the whole /dev/block/mmcblk0 partition and seeing if you can unpack it then.
Click to expand...
Click to collapse
There is one thing I noted in the partition list. the stating point for boot, recovery and sec_ro is same i.e:
Code:
0x0000000000600000
but they end at different blocks, would that be a problem?
I think the over all partition type is ext4 which is supported by Ubuntu 13.04, can i do something to read the partition directly, like mount it in some way?
ssm14293 said:
Hi I tried to extract the recovery.img created from your command using unmkboot in my Ubuntu VM. I got two files from it, a zImage file and an initramfs.cpio.gz files with this output:
Code:
unmkbootimg version 1.2 - Mikael Q Kuisma <[email protected]>
File ./images/recovery.img not a plain boot image, seeking for embedded image ... found!
Kernel size 3248084
Kernel address 0x10008000
Ramdisk size 506660
Ramdisk address 0x11000000
Secondary size 0
Secondary address 0x10f00000
Kernel tags address 0x10000100
Flash page size 2048
Board name is "1354555027"
Command line ""
This image is built using standard mkbootimg
Extracting kernel to file zImage ...
Extracting root filesystem to file initramfs.cpio.gz ...
All done.
---------------
To recompile this image, use:
mkbootimg --kernel zImage --ramdisk initramfs.cpio.gz --board '1354555027' -o new_boot.img
---------------
Now what can i do from here. I cannot extract the cpio.gz file, how will I do that.
Thanks for helping out!
I cannot dump the whole mmcblk0 because I dont have a memory card large enough for the dump, which is roughly 4gb.
Regards
Click to expand...
Click to collapse
To unpack the cpio.gz file I would recommend downloading these Linux boot.img tools, they will allow you to unpack and repack the cpio.gz ramdisk file. Make sure after you download those tools you put them in your ~/bin folder and that the folder in your PATH or else the tools won't work as they rely on each other to function properly.
ssm14293 said:
There is one thing I noted in the partition list. the stating point for boot, recovery and sec_ro is same i.e:
Code:
0x0000000000600000
but they end at different blocks, would that be a problem?
I think the over all partition type is ext4 which is supported by Ubuntu 13.04, can i do something to read the partition directly, like mount it in some way?
Click to expand...
Click to collapse
I thought this offset for the partitions was very interesting, instead of going from one offset to another that would make it clear which parts of the /dev/block/mmcblk0 is recovery, boot, etc. they all seem to overlap. If you can find to dump the full partition and then transfer it to your computer you should be able to mount it in Ubuntu if it's ext4 and then read it's contents.
Found a way!
shimp208 said:
To unpack the cpio.gz file I would recommend downloading these Linux boot.img tools, they will allow you to unpack and repack the cpio.gz ramdisk file. Make sure after you download those tools you put them in your ~/bin folder and that the folder in your PATH or else the tools won't work as they rely on each other to function properly.
I thought this offset for the partitions was very interesting, instead of going from one offset to another that would make it clear which parts of the /dev/block/mmcblk0 is recovery, boot, etc. they all seem to overlap. If you can find to dump the full partition and then transfer it to your computer you should be able to mount it in Ubuntu if it's ext4 and then read it's contents.
Click to expand...
Click to collapse
Hi again!!
I just got myself an 8GB memory card. I also searched more about nandroid backups for non-CWM phones. I got across onandroid, it creates img files of all partitions. It was created by someone from XDA Forums, can't remember the name. So at the moment it is generating MD5 Checksum.
After this I will create my OWN Rom and CWM for this phone :victory: , well after my finals .
Thanks for your help! :highfive:
For all Qmobile Rooted users, use onandroid to create backups, but at your own risk. I can confirm for QMobiel A5 Classic
where to copy symphony CWM recovery.img using dd command
I am Moniruzzaman from Dhaka, Bangladesh...
Please forgive me for my weak English.
I have created a CWM recovery img (Latest Touch Version) for my rooted Symphony W85. My device partitions is similar to the Qmoible A5Classic. Now I have failed to copy it to the recovery partition as i could not figure out which is my recovery partition.
Partition Information:
preloader 0x0000000000040000 0x0000000000000000 2 /dev/misc-sd
dsp_bl 0x00000000005c0000 0x0000000000040000 2 /dev/misc-sd
mbr 0x0000000000004000 0x0000000000000000 2 /dev/block/mmcblk0
ebr1 0x000000000005c000 0x0000000000004000 2 /dev/block/mmcblk0p1
pmt 0x0000000000400000 0x0000000000060000 2 /dev/block/mmcblk0
nvram 0x0000000000300000 0x0000000000460000 2 /dev/block/mmcblk0
seccfg 0x0000000000020000 0x0000000000760000 2 /dev/block/mmcblk0
uboot 0x0000000000060000 0x0000000000780000 2 /dev/block/mmcblk0
bootimg 0x0000000000600000 0x00000000007e0000 2 /dev/block/mmcblk0
recovery 0x0000000000600000 0x0000000000de0000 2 /dev/block/mmcblk0
sec_ro 0x0000000000600000 0x00000000013e0000 2 /dev/block/mmcblk0p5
misc 0x0000000000060000 0x00000000019e0000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000001a40000 2 /dev/block/mmcblk0
expdb 0x00000000000a0000 0x0000000001d40000 2 /dev/block/mmcblk0
ebr2 0x0000000000004000 0x0000000001de0000 2 /dev/block/mmcblk0
android 0x0000000020100000 0x0000000001de4000 2 /dev/block/mmcblk0p6
cache 0x000000000a100000 0x0000000021ee4000 2 /dev/block/mmcblk0p2
usrdata 0x0000000041100000 0x000000002bfe4000 2 /dev/block/mmcblk0p3
fat 0x0000000000000001 0x000000006d0e4000 2 /dev/block/mmcblk0p4
bmtpool 0x000000007bafbfff 0xffffffffffa00000 2 /dev/block/mmcblk0
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc boot (null) 0
2 /cache ext4 /dev/block/mmcblk0p2 (null) 0
3 /data ext4 /dev/block/mmcblk0p3 (null) 0
4 /misc emmc misc (null) 0
5 /recovery emmc recovery (null) 0
6 /sdcard vfat /dev/block/mmcblk1 /dev/block/mmcblk0p4 0
7 /sdcard2 vfat /dev/block/mmcblk0p4 (null) 0
8 /system ext4 /dev/block/mmcblk0p6 (null) 0
I have flashed the recovery.img using dd if=mnt/sdcard/recovery.img of=/dev/recovery. Everything was fine except my gsm signal was gone.
Then I tried flashed stock recovery.img using dd if=mnt/sdcard/recovery.img of=/dev/recovery - everything works fine again.
I have come so far and now i can't fine the right partitions. I am very frustrated.
Can any one please help me how to flash my CWM recovery img (Latest Touch Version) to my device as it is combined partitions.
shimp208 said:
.
Click to expand...
Click to collapse
What about this: this is from Lenovo TAB S8-50 (USA/BestBuy) Wifi version....
Starting recovery on Thu Dec 4 03:55:45 2014
recovery filesystem table
=========================
0 /reserved hidden /dev/block/platform/intel/by-label/reserved 0
1 /ESP vfat /dev/block/platform/intel/by-label/ESP 0
2 /boot hidden /dev/block/platform/intel/by-label/boot 0
3 /recovery hidden /dev/block/platform/intel/by-label/recovery 0
4 /fastboot hidden /dev/block/platform/intel/by-label/fastboot 0
5 /reserved_1 hidden /dev/block/platform/intel/by-label/reserved_1 0
6 /panic raw /dev/block/platform/intel/by-label/panic 0
7 /factory ext4 /dev/block/platform/intel/by-label/factory 0
8 /misc emmc /dev/block/platform/intel/by-label/misc 0
9 /config ext4 /dev/block/platform/intel/by-label/config 0
10 /cache ext4 /dev/block/platform/intel/by-label/cache 0
11 /system ext4 /dev/block/platform/intel/by-label/system 0
12 /data ext4 /dev/block/platform/intel/by-label/data -16384
13 /sdcard vfat /dev/block/mmcblk1p1 0
14 /tmp ramdisk ramdisk 0
jazzespresso said:
What about this: this is from Lenovo TAB S8-50 (USA/BestBuy) Wifi version....
Starting recovery on Thu Dec 4 03:55:45 2014
recovery filesystem table
=========================
0 /reserved hidden /dev/block/platform/intel/by-label/reserved 0
1 /ESP vfat /dev/block/platform/intel/by-label/ESP 0
2 /boot hidden /dev/block/platform/intel/by-label/boot 0
3 /recovery hidden /dev/block/platform/intel/by-label/recovery 0
4 /fastboot hidden /dev/block/platform/intel/by-label/fastboot 0
5 /reserved_1 hidden /dev/block/platform/intel/by-label/reserved_1 0
6 /panic raw /dev/block/platform/intel/by-label/panic 0
7 /factory ext4 /dev/block/platform/intel/by-label/factory 0
8 /misc emmc /dev/block/platform/intel/by-label/misc 0
9 /config ext4 /dev/block/platform/intel/by-label/config 0
10 /cache ext4 /dev/block/platform/intel/by-label/cache 0
11 /system ext4 /dev/block/platform/intel/by-label/system 0
12 /data ext4 /dev/block/platform/intel/by-label/data -16384
13 /sdcard vfat /dev/block/mmcblk1p1 0
14 /tmp ramdisk ramdisk 0
Click to expand...
Click to collapse
I would recommend running the following command to dump your recovery partition:
Code:
cat /dev/block/platform/intel/by-label/recovery > /mnt/sdcard/recovery.img
Let me know if you still have questions, happy to help you out.
shimp208 said:
I would recommend running the following command to dump your recovery partition:
Code:
cat /dev/block/platform/intel/by-label/recovery > /mnt/sdcard/recovery.img
Let me know if you still have questions, happy to help you out.
Click to expand...
Click to collapse
thank you very much...what about boot.img?
jazzespresso said:
thank you very much...what about boot.img?
Click to expand...
Click to collapse
For boot you would run the command:
Code:
cat /dev/block/platform/intel/by-label/boot > /mnt/sdcard/boot.img
Hope this helps you!
Can anyone help me ? I ran the script bellow trying to expand my system partition to solve a problem and now I've lost my recoverymode. I get a 2 min blackscreen and then it starts.
COde that got me lost:
Code:
#!/sbin/sh
OUTFD=$2
ui_print() {
echo -n -e "ui_print $1\n" > /proc/self/fd/$OUTFD
echo -n -e "ui_print\n" > /proc/self/fd/$OUTFD
}
ui_print ""
ui_print "###########################"
ui_print "# audahadi #"
ui_print "# modded from forumber2's #"
ui_print "# Repartition script #"
ui_print "# Mi 3W /system 1.2G #"
ui_print "# only! #"
ui_print "###########################"
ui_print ""
ui_print "Unmounting systems partiton..."
umount -l /system
umount -l /system1
umount -l /dev/block/mmcblk0p25
umount -l /dev/block/mmcblk0p26
ui_print ""
ui_print "WARNING! System is ready, repartitioning will start in
2 seconds"
sleep 2
ui_print ""
ui_print "Removing partitions..."
parted /dev/block/mmcblk0 rm 25
parted /dev/block/mmcblk0 rm 26
ui_print "Removing partitions...COMPLETED"
ui_print ""
ui_print "Creating new partitions..."
parted /dev/block/mmcblk0 mkpart primary 403MB 1740MB
parted /dev/block/mmcblk0 mkpart primary 1740MB 1745MB
parted /dev/block/mmcblk0 name 25 system
parted /dev/block/mmcblk0 name 26 system1
ui_print "Creating new partitions...COMPLETED"
ui_print ""
ui_print "Unmounting systems partitions again..."
umount -l /system
umount -l /system1
umount -l /dev/block/mmcblk0p25
umount -l /dev/block/mmcblk0p26
ui_print "Unmounting systems partitions again...COMPLETED"
ui_print ""
ui_print "Formatting new partitions..."
mke2fs -b 4096 -T ext4 /dev/block/mmcblk0p25
mke2fs -b 4096 -T ext4 /dev/block/mmcblk0p26
ui_print "Formatting new partitions...COMPLETED."
ui_print ""
ui_print "ALL DONE!..."
ui_print ""
ui_print "Rebooting to recovery in 5 seconds..."
ui_print "Thanks to forumber2 for his original GT-i9300
repartition script"
sleep 5
reboot recovery
fi
Follow info:
Code:
[email protected]:/ $ cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 65536 mmcblk0p1
179 2 512 mmcblk0p2
179 3 512 mmcblk0p3
179 4 2048 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 24576 mmcblk0p7
179 8 512 mmcblk0p8
179 9 1 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 780 mmcblk0p12
179 13 780 mmcblk0p13
179 14 780 mmcblk0p14
179 15 8192 mmcblk0p15
179 16 8192 mmcblk0p16
179 17 8 mmcblk0p17
179 18 16384 mmcblk0p18
179 19 16384 mmcblk0p19
179 20 512 mmcblk0p20
179 21 512 mmcblk0p21
179 22 1556480 mmcblk0p22
179 23 819200 mmcblk0p23
179 24 26714112 mmcblk0p24
179 27 24576 mmcblk0p27
179 28 3072 mmcblk0p28
179 29 8 mmcblk0p29
179 30 32768 mmcblk0p30
179 31 32768 mmcblk0p31
259 0 512 mmcblk0p32
259 1 512 mmcblk0p33
259 2 16384 mmcblk0p34
259 3 879599 mmcblk0p35
[email protected]:/ $
Code:
[email protected]:/dev/block/platform/msm_sdcc.1/by-name # ls -l
ls -l
lrwxrwxrwx root root 2015-07-20 22:30 DDR -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2015-07-20 22:30 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-07-20 22:30 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-07-20 22:30 cache -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2015-07-20 22:30 drm -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-07-20 22:30 eksst -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-07-20 22:30 encrypt -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-07-20 22:30 factory -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-07-20 22:30 fota -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 2015-07-20 22:30 fsg -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2015-07-20 22:30 grow -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 2015-07-20 22:30 m9kefs1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-07-20 22:30 m9kefs2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-07-20 22:30 m9kefs3 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-07-20 22:30 misc -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-07-20 22:30 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-07-20 22:30 modemst1 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-07-20 22:30 modemst2 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-07-20 22:30 mpt -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 2015-07-20 22:30 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-07-20 22:30 recovery -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2015-07-20 22:30 reserved -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 2015-07-20 22:30 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-07-20 22:30 rpmbak -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 2015-07-20 22:30 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-07-20 22:30 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-07-20 22:30 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-07-20 22:30 sns -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-07-20 22:30 ssd -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-07-20 22:30 system -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2015-07-20 22:30 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-07-20 22:30 tzbak -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 2015-07-20 22:30 userdata -> /dev/block/mmcblk0p24
[email protected]:/dev/block/platform/msm_sdcc.1/by-name #
Code:
[email protected]:/dev/block $ cat /proc/mounts
cat /proc/mounts
rootfs / rootfs ro,seclabel,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,seclabel,relatime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,
data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,node
v,noatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,no
dev,noatime,noauto_da_alloc,data=ordered 0 0
[email protected]:/dev/block $
dihhedessa said:
Can anyone help me ? I ran the script bellow trying to expand my system partition to solve a problem and now I've lost my recoverymode. I get a 2 min blackscreen and then it starts.
COde that got me lost:
Code:
#!/sbin/sh
OUTFD=$2
ui_print() {
echo -n -e "ui_print $1\n" > /proc/self/fd/$OUTFD
echo -n -e "ui_print\n" > /proc/self/fd/$OUTFD
}
ui_print ""
ui_print "###########################"
ui_print "# audahadi #"
ui_print "# modded from forumber2's #"
ui_print "# Repartition script #"
ui_print "# Mi 3W /system 1.2G #"
ui_print "# only! #"
ui_print "###########################"
ui_print ""
ui_print "Unmounting systems partiton..."
umount -l /system
umount -l /system1
umount -l /dev/block/mmcblk0p25
umount -l /dev/block/mmcblk0p26
ui_print ""
ui_print "WARNING! System is ready, repartitioning will start in
2 seconds"
sleep 2
ui_print ""
ui_print "Removing partitions..."
parted /dev/block/mmcblk0 rm 25
parted /dev/block/mmcblk0 rm 26
ui_print "Removing partitions...COMPLETED"
ui_print ""
ui_print "Creating new partitions..."
parted /dev/block/mmcblk0 mkpart primary 403MB 1740MB
parted /dev/block/mmcblk0 mkpart primary 1740MB 1745MB
parted /dev/block/mmcblk0 name 25 system
parted /dev/block/mmcblk0 name 26 system1
ui_print "Creating new partitions...COMPLETED"
ui_print ""
ui_print "Unmounting systems partitions again..."
umount -l /system
umount -l /system1
umount -l /dev/block/mmcblk0p25
umount -l /dev/block/mmcblk0p26
ui_print "Unmounting systems partitions again...COMPLETED"
ui_print ""
ui_print "Formatting new partitions..."
mke2fs -b 4096 -T ext4 /dev/block/mmcblk0p25
mke2fs -b 4096 -T ext4 /dev/block/mmcblk0p26
ui_print "Formatting new partitions...COMPLETED."
ui_print ""
ui_print "ALL DONE!..."
ui_print ""
ui_print "Rebooting to recovery in 5 seconds..."
ui_print "Thanks to forumber2 for his original GT-i9300
repartition script"
sleep 5
reboot recovery
fi
Follow info:
Code:
[email protected]:/ $ cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 65536 mmcblk0p1
179 2 512 mmcblk0p2
179 3 512 mmcblk0p3
179 4 2048 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 24576 mmcblk0p7
179 8 512 mmcblk0p8
179 9 1 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 780 mmcblk0p12
179 13 780 mmcblk0p13
179 14 780 mmcblk0p14
179 15 8192 mmcblk0p15
179 16 8192 mmcblk0p16
179 17 8 mmcblk0p17
179 18 16384 mmcblk0p18
179 19 16384 mmcblk0p19
179 20 512 mmcblk0p20
179 21 512 mmcblk0p21
179 22 1556480 mmcblk0p22
179 23 819200 mmcblk0p23
179 24 26714112 mmcblk0p24
179 27 24576 mmcblk0p27
179 28 3072 mmcblk0p28
179 29 8 mmcblk0p29
179 30 32768 mmcblk0p30
179 31 32768 mmcblk0p31
259 0 512 mmcblk0p32
259 1 512 mmcblk0p33
259 2 16384 mmcblk0p34
259 3 879599 mmcblk0p35
[email protected]:/ $
Code:
[email protected]:/dev/block/platform/msm_sdcc.1/by-name # ls -l
ls -l
lrwxrwxrwx root root 2015-07-20 22:30 DDR -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2015-07-20 22:30 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-07-20 22:30 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-07-20 22:30 cache -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2015-07-20 22:30 drm -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-07-20 22:30 eksst -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-07-20 22:30 encrypt -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-07-20 22:30 factory -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-07-20 22:30 fota -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 2015-07-20 22:30 fsg -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2015-07-20 22:30 grow -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 2015-07-20 22:30 m9kefs1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-07-20 22:30 m9kefs2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-07-20 22:30 m9kefs3 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-07-20 22:30 misc -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-07-20 22:30 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-07-20 22:30 modemst1 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-07-20 22:30 modemst2 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-07-20 22:30 mpt -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 2015-07-20 22:30 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-07-20 22:30 recovery -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2015-07-20 22:30 reserved -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 2015-07-20 22:30 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-07-20 22:30 rpmbak -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 2015-07-20 22:30 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-07-20 22:30 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-07-20 22:30 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-07-20 22:30 sns -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-07-20 22:30 ssd -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-07-20 22:30 system -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2015-07-20 22:30 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-07-20 22:30 tzbak -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 2015-07-20 22:30 userdata -> /dev/block/mmcblk0p24
[email protected]:/dev/block/platform/msm_sdcc.1/by-name #
Code:
[email protected]:/dev/block $ cat /proc/mounts
cat /proc/mounts
rootfs / rootfs ro,seclabel,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,seclabel,relatime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,
data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,node
v,noatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,no
dev,noatime,noauto_da_alloc,data=ordered 0 0
[email protected]:/dev/block $
Click to expand...
Click to collapse
@shimp208 and @jazzespresso maybe you guys could please help me? I am desperate!
Hi there,
I've the same problem, recovery is in mmcblk0, someone can help me please ? I can't find any solutions.
AndroGeek
Partion info of a my 6735 rooted android device
How can I get "dumchar_info", or "Part_Name ,Size ,StartAddr,Type,Map,To" info with adb command of a rooted mt6735 device with 5.1 lollipop? Thanks a lot in anticipation.
Hi all,
I am not able to enter in recovery mode after a mistaken deletion from partitions /dev/block/mmcblk0p25 and /dev/block/mmcblk0p26 which I belive in Optimus G is persist (since I lost my wifi and network signal) and tombstones partitions. Neither my sdcard mount.
I already tried to restore through odin , lg software tool but it does not recognize my phone when I connect on PC even thought all usb drivers installed and I am able to acess adb tools and shell recognizing my device when I plug into pc. Now I am stuck on a system without recovery mode, internet, sdcard, signal and when I try to flash a new ROM or recovery with adb it does not recognize the recovery partition and when I tried to create the persist partition it says that the device (/dev/block/mmcblk0p25) does not exist. Any guesses?
Jessooca said:
First.... let me say I'm sorry to hear about your issue. To be clear, you cannot get the Optimus G to boot at all, correct? You have a black as the night, phone. Nothing shows up on the screen whatsoever?
Did you backup any of the partitions before you decided to mess with your phone? Did you use FreeGee to back up the efs partitions?
IF you have any signs of life, I would strongly advise you contact TheCubed he is definitely the person you want to talk to about your issue, write him a message and when you do, be very detailed about what your device does or doesn't do, etc... He'll need to know all of that information to give you a proper response.
Jessica
Click to expand...
Click to collapse
Hi Jessica, thanks for your response! I really appreciate!
So this is strange, because In fact I can boot and I can entry on my bootloader and ROM although none of it can save my life. Neither the watch stays correctly now
But when I try to enter in recovery mode or open freegee app it is all black. And when I start the phone it took about 2 minutes black and then cyano ran. And I am really dead since I didn't backed nothing up before. :'( (but my EFS partitions seems ok)
The mess began when I tried to resize system partition to install an cyano nightly update. This was the code I ran
Code:
ui_print ""
ui_print "Unmounting systems partiton..."
umount -l /system
umount -l /system1
umount -l /dev/block/mmcblk0p25
umount -l /dev/block/mmcblk0p26
ui_print ""
ui_print "WARNING! System is ready, repartitioning will start in 2 seconds"
sleep 2
ui_print ""
ui_print "Removing partitions..."
parted /dev/block/mmcblk0 rm 25
parted /dev/block/mmcblk0 rm 26
ui_print "Removing partitions...COMPLETED"
ui_print ""
ui_print "Creating new partitions..."
parted /dev/block/mmcblk0 mkpart primary 403MB 1740MB
parted /dev/block/mmcblk0 mkpart primary 1740MB 1745MB
parted /dev/block/mmcblk0 name 25 system
parted /dev/block/mmcblk0 name 26 system1
ui_print "Creating new partitions...COMPLETED"
ui_print ""
ui_print "Unmounting systems partitions again..."
umount -l /system
umount -l /system1
umount -l /dev/block/mmcblk0p25
umount -l /dev/block/mmcblk0p26
ui_print "Unmounting systems partitions again...COMPLETED"
ui_print ""
ui_print "Formatting new partitions..."
mke2fs -b 4096 -T ext4 /dev/block/mmcblk0p25
mke2fs -b 4096 -T ext4 /dev/block/mmcblk0p26
ui_print "Formatting new partitions...COMPLETED."
ui_print ""
ui_print "ALL DONE!..."
ui_print ""
ui_print "Rebooting to recovery in 5 seconds..."
ui_print "Thanks to forumber2 for his original GT-i9300 repartition script"
sleep 5
reboot recovery
fi
I was so stupid and noob that at the time I did not realized that this code was not to Optimus G.
Without a recovery mode and internet I am completely stuck
I gonna try to reach him! thank you for your attention!
My "Phone"
LG_E975
cyanogemMod version: 11-20141115-SNAPSHOT-M12-E975
android : 4.4.4.
kernel version: 3.4.0-CM+
Jessooca said:
Have you used the KDZ or TOT file for your phone and tried to restore it yet using lg tools? I have a whole step by step tutorial that you can follow, for any lg device.
When you plug your phone into your computer does the computer detect the phone, what about ADB, does it detect your device?
Click to expand...
Click to collapse
Hi Jessica,
I've tried some of lg tools but any pc doesn't recognize my phone... but adb interface does recognize. I am able to enter on my phone through adb shell. I have all the last lg usb drivers installed and already tried in more than one PC and still nothing. None of them recognize my phone when plugged. I've tried in odin, pc suite, lg mobile device, lg flashtool... it sucks! If only I could get a way to connect it on a PC door then I could try something with a program called qpst configuration or lg tools.
But let me take a look at your tutorial! it worth the shot! Thanks for your answers!
Jessooca said:
Before i go any further, I'll look into a POSSIBLE solution but i need to know which device you have exactly (country version as well) and what's the latest update and/or boot loader you were on when this happened.
If you have an LG device you can't use Odin. That's a Samsung tool.
Whatever you do, since it's recognized via adb do not uninstall or remove anything from your computer. If you lose adb access then you may end up screwed entirely.
-Jessica
Click to expand...
Click to collapse
Hi Jessica, follow my information's. I don't know if there is something sensitive I shouldn't put here. I removed my ESN, IMEI and MSN. If you need it just let me know.
<response req_cmd="auth_model_check" status="OK">
<auth_model_check>
<result>OK</result>
<model>LGE977</model>
<suffix>ABRABL</suffix>
<esn_date/>
<sw_version>E97720A_00</sw_version>
<sw_url>
http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW964116432109876543213/E97720A_00.kdz
</sw_url>
<sw_locale_url/>
<sw_recommand_uri/>
<app_version/>
<app_url/>
<cs_em_flag>N</cs_em_flag>
<cs_em_uri>N</cs_em_uri>
<chip_type>EG</chip_type>
<prod_type>GSM</prod_type>
<buyer>BRA</buyer>
<file_name>E97720A_00.kdz</file_name>
</auth_model_check>
</response>
And also my device name is this?! /msm_sdcc.1
Follow some other relevant information. Notice that partitions /dev/block/mmcblk0p25 and /dev/block/mmcblk0p26 are gone
Code:
[email protected]:/ #
[email protected]:/ # cat /proc/mounts
cat /proc/mounts
rootfs / rootfs ro,seclabel,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,seclabel,relatime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,data=ordered 0 0
[email protected]:/ #
[email protected]:/ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 65536 mmcblk0p1
179 2 512 mmcblk0p2
179 3 512 mmcblk0p3
179 4 2048 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 24576 mmcblk0p7
179 8 512 mmcblk0p8
179 9 1 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 780 mmcblk0p12
179 13 780 mmcblk0p13
179 14 780 mmcblk0p14
179 15 8192 mmcblk0p15
179 16 8192 mmcblk0p16
179 17 8 mmcblk0p17
179 18 16384 mmcblk0p18
179 19 16384 mmcblk0p19
179 20 512 mmcblk0p20
179 21 512 mmcblk0p21
179 22 1556480 mmcblk0p22
179 23 819200 mmcblk0p23
179 24 26714112 mmcblk0p24
179 27 24576 mmcblk0p27
179 28 3072 mmcblk0p28
179 29 8 mmcblk0p29
179 30 32768 mmcblk0p30
179 31 32768 mmcblk0p31
259 0 512 mmcblk0p32
259 1 512 mmcblk0p33
259 2 16384 mmcblk0p34
259 3 879599 mmcblk0p35
[email protected]:/ #
[email protected]:/ # cat /dev/block/platform/m*/by-name
cat /dev/block/platform/m*/by-name
/system/bin/sh: cat: /dev/block/platform/msm_sdcc.1/by-name: Is a directory
1|[email protected]:/ # cat /dev/block/platform/ms*/by-name
cat /dev/block/platform/ms*/by-name
/system/bin/sh: cat: /dev/block/platform/msm_sdcc.1/by-name: Is a directory
1|[email protected]:/ # cd /dev/block/platform/ms*/by-name
cd /dev/block/platform/ms*/by-name
[email protected]:/dev/block/platform/msm_sdcc.1/by-name # ls -la
ls -la
lrwxrwxrwx root root 1970-01-02 08:54 DDR -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-02 08:54 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-02 08:54 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-02 08:54 cache -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-02 08:54 drm -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-02 08:54 eksst -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-02 08:54 encrypt -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-02 08:54 factory -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-02 08:54 fota -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-02 08:54 fsg -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-02 08:54 grow -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-02 08:54 m9kefs1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-02 08:54 m9kefs2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-02 08:54 m9kefs3 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-02 08:54 misc -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-02 08:54 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-02 08:54 modemst1 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-02 08:54 modemst2 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-02 08:54 mpt -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-02 08:54 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-02 08:54 recovery -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-02 08:54 reserved -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-02 08:54 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-02 08:54 rpmbak -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-02 08:54 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-02 08:54 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-02 08:54 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-02 08:54 sns -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-02 08:54 ssd -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-02 08:54 system -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-02 08:54 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-02 08:54 tzbak -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-02 08:54 userdata -> /dev/block/mmcblk0p24
[email protected]:/dev/block/platform/msm_sdcc.1/by-name #
Trying with odin. Such a stupid rookie! thanks again for the tip!! :good:
So, my bootloader:
PRODUCT_NAME - mako
VARIANT - mako 32GB
HW VERSION - rev_12 (136)
BOOTLOADER VERSION - N/A
CARRIER INFO - None
SERIAL NUMBER - 07a4bf02964ac951
SIGNING - production
SECURE BOOT - enabled
LOCK STATE - unlocked
Hi Jessica!!
my bootloader is locked? but is says unlocked on "locked state"
About the model, e977 is the e975(int) version sold in brazil. I dont know why in some places shows up as e977 and other e975. When I used to flash cyano rom I downloaded the versions from e975 since there was no one for e977, so maybe is that
Sorry for delay, had a family issue last week, thanks for your help!
I am getting a Galaxy View on Monday but in the mean time i have made a basic twrp tree can someone run these commands on there device so i can get the partition sizes .
Code:
adb shell
ls -al /dev/block/platform/13540000.dwmmc0/by-name
deadman96385 said:
I am getting a Galaxy View on Monday but in the mean time i have made a basic twrp tree can someone run these commands on there device so i can get the partition sizes .
Click to expand...
Click to collapse
Do you still need this done..?.. I have the Verizon Version of the Galaxy View.
justjayhere said:
Do you still need this done..?.. I have the Verizon Version of the Galaxy View.
Click to expand...
Click to collapse
I have gotten the sizes still working on getting twrp to boot.
deadman96385 said:
I have gotten the sizes still working on getting twrp to boot.
Click to expand...
Click to collapse
I am looking forward to getting root for Galaxy View.
justjayhere said:
I am looking forward to getting root for Galaxy View.
Click to expand...
Click to collapse
@ashyx and I have gotten the wifi variant to boot twrp can you grab the partition sizes for your tablet just run these commands and paste there output here or in a pastebin
Code:
adb shell
ls -al /dev/block/platform/13540000.dwmmc0/by-name
cat /proc/partitions
deadman96385 said:
@ashyx and I have gotten the wifi variant to boot twrp can you grab the partition sizes for your tablet just run these commands and paste there output here or in a pastebin
Click to expand...
Click to collapse
I will do so later today...currently out of town.
Verizon 4G 64GB version Partition Info
deadman96385 said:
I am getting a Galaxy View on Monday but in the mean time i have made a basic twrp tree can someone run these commands on there device so i can get the partition sizes .
Code:
adb shell
ls -al /dev/block/platform/13540000.dwmmc0/by-name
Click to expand...
Click to collapse
Verizon 4G 64GB version...
Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ $ ls -al /dev/block/platform/13540000.dwmmc0/by-name
ls -al /dev/block/platform/13540000.dwmmc0/by-name
lrwxrwxrwx root root 2016-10-06 15:51 BOOT -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2016-10-06 15:51 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2016-10-06 15:51 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2016-10-06 15:51 CACHE -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2016-10-06 15:51 CARRIER -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2016-10-06 15:51 CDMA-RADIO -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2016-10-06 15:51 CPEFS -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2016-10-06 15:51 DNT -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2016-10-06 15:51 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2016-10-06 15:51 OTA -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2016-10-06 15:51 PARAM -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2016-10-06 15:51 PERSDATA -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2016-10-06 15:51 PERSISTENT -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2016-10-06 15:51 RADIO -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2016-10-06 15:51 RECOVERY -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2016-10-06 15:51 RESERVED2 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2016-10-06 15:51 SYSTEM -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2016-10-06 15:51 TOMBSTONES -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2016-10-06 15:51 USERDATA -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2016-10-06 15:51 m9kefs1 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2016-10-06 15:51 m9kefs2 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2016-10-06 15:51 m9kefs3 -> /dev/block/mmcblk0p7
[email protected]:/ $ cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 61071360 mmcblk0
179 1 4096 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 4096 mmcblk0p7
259 0 15360 mmcblk0p8
259 1 8192 mmcblk0p9
259 2 32768 mmcblk0p10
259 3 38912 mmcblk0p11
259 4 8192 mmcblk0p12
259 5 4096 mmcblk0p13
259 6 90112 mmcblk0p14
259 7 1024 mmcblk0p15
259 8 1024 mmcblk0p16
259 9 512 mmcblk0p17
259 10 12288 mmcblk0p18
259 11 2560 mmcblk0p19
259 12 3072000 mmcblk0p20
259 13 1048576 mmcblk0p21
259 14 56676352 mmcblk0p22
179 24 4096 mmcblk0rpmb
179 16 4096 mmcblk0boot1
179 8 4096 mmcblk0boot0
253 0 1048576 vnswap0
[email protected]:/ $
justjayhere said:
Verizon 4G 64GB version...
Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ $ ls -al /dev/block/platform/13540000.dwmmc0/by-name
ls -al /dev/block/platform/13540000.dwmmc0/by-name
lrwxrwxrwx root root 2016-10-06 15:51 BOOT -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2016-10-06 15:51 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2016-10-06 15:51 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2016-10-06 15:51 CACHE -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2016-10-06 15:51 CARRIER -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2016-10-06 15:51 CDMA-RADIO -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2016-10-06 15:51 CPEFS -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2016-10-06 15:51 DNT -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2016-10-06 15:51 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2016-10-06 15:51 OTA -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2016-10-06 15:51 PARAM -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2016-10-06 15:51 PERSDATA -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2016-10-06 15:51 PERSISTENT -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2016-10-06 15:51 RADIO -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2016-10-06 15:51 RECOVERY -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2016-10-06 15:51 RESERVED2 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2016-10-06 15:51 SYSTEM -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2016-10-06 15:51 TOMBSTONES -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2016-10-06 15:51 USERDATA -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2016-10-06 15:51 m9kefs1 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2016-10-06 15:51 m9kefs2 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2016-10-06 15:51 m9kefs3 -> /dev/block/mmcblk0p7
[email protected]:/ $ cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 61071360 mmcblk0
179 1 4096 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 4096 mmcblk0p7
259 0 15360 mmcblk0p8
259 1 8192 mmcblk0p9
259 2 32768 mmcblk0p10
259 3 38912 mmcblk0p11
259 4 8192 mmcblk0p12
259 5 4096 mmcblk0p13
259 6 90112 mmcblk0p14
259 7 1024 mmcblk0p15
259 8 1024 mmcblk0p16
259 9 512 mmcblk0p17
259 10 12288 mmcblk0p18
259 11 2560 mmcblk0p19
259 12 3072000 mmcblk0p20
259 13 1048576 mmcblk0p21
259 14 56676352 mmcblk0p22
179 24 4096 mmcblk0rpmb
179 16 4096 mmcblk0boot1
179 8 4096 mmcblk0boot0
253 0 1048576 vnswap0
[email protected]:/ $
Click to expand...
Click to collapse
I would say try the wifi build but i can't recommend it due to there not being any firmware builds for the Verizon variant so i can't get a stock recovery image from it in case it doesn't work.
ValueError: malformed recovery.fstab line: "/boot emmc /dev/block/platform/sprd-sdhci
I need help with compiling CM-13 for my device, I've been following AlaskaLinuxUser's guide for building the device tree from scratch. I'm stuck at one point when building that I just can't figure out though, can anyone help me please?
Made recovery image: /home/raid/android/system/out/target/product/goyave3g/recovery.img
Target build info: /home/raid/android/system/out/target/product/goyave3g/system/build.prop
Construct recovery from boot
mkdir -p /home/raid/android/system/out/target/product/goyave3g/obj/PACKAGING/recovery_patch_intermediates/
PATH=/home/raid/android/system/out/host/linux-x86/bin:$PATH /home/raid/android/system/out/host/linux-x86/bin/imgdiff /home/raid/android/system/out/target/product/goyave3g/boot.img /home/raid/android/system/out/target/product/goyave3g/recovery.img /home/raid/android/system/out/target/product/goyave3g/obj/PACKAGING/recovery_patch_intermediates/recovery_from_boot.p
build/tools/generate-notice-files.py /home/raid/android/system/out/target/product/goyave3g/obj/NOTICE.txt /home/raid/android/system/out/target/product/goyave3g/obj/NOTICE.html "Notices for files contained in the filesystem images in this directory:" /home/raid/android/system/out/target/product/goyave3g/obj/NOTICE_FILES/src
failed to reconstruct target deflate chunk 1 [(null)]; treating as normal
chunk 0: type 0 start 0 len 5230602
chunk 1: type 2 start 5230602 len 1732096
chunk 2: type 0 start 6193783 len 269705
Construct patches for 3 chunks...
Combining NOTICE files into HTML
Combining NOTICE files into text
patch 0 is 206 bytes (of 5230602)
patch 1 is 1730987 bytes (of 963181)
patch 2 is 196 bytes (of 269705)
chunk 0: normal ( 0, 5230602) 206
chunk 1: deflate ( 5230602, 3389635) 1730987 (null)
chunk 2: normal ( 8620237, 270131) 196
Installing recovery patch to system partition
Traceback (most recent call last):
File "./build/tools/releasetools/make_recovery_patch", line 55, in <module>
main(sys.argv[1:])
File "./build/tools/releasetools/make_recovery_patch", line 37, in main
OPTIONS.info_dict = common.LoadInfoDict(input_dir)
File "/home/raid/android/system/build/tools/releasetools/common.py", line 201, in LoadInfoDict
d["fstab"] = LoadRecoveryFSTab(read_helper, d["fstab_version"], d["device_type"])
File "/home/raid/android/system/build/tools/releasetools/common.py", line 285, in LoadRecoveryFSTab
raise ValueError("malformed recovery.fstab line: "%s"" % (line,))
ValueError: malformed recovery.fstab line: "/boot emmc /dev/block/platform/sprd-sdhci.3/by-name/KERNEL"
build/core/Makefile:1074: recipe for target '/home/raid/android/system/out/target/product/goyave3g/system/bin/install-recovery.sh' failed
make: *** [/home/raid/android/system/out/target/product/goyave3g/system/bin/install-recovery.sh] Error 1
make: Leaving directory '/home/raid/android/system'
#### make failed to build some targets (03:18 (mm:ss)) ####
Click to expand...
Click to collapse
This is what is in my recovery.fstab
/boot emmc /dev/block/platform/sprd-sdhci.3/by-name/KERNEL
/system ext4 /dev/block/platform/sprd-sdhci.3/by-name/system
/data ext4 /dev/block/platform/sprd-sdhci.3/by-name/userdata flags=length=-16384
/cache ext4 /dev/block/platform/sprd-sdhci.3/by-name/CSC
/recovery emmc /dev/block/platform/sprd-sdhci.3/by-name/RECOVERY
/efs emmc /dev/block/platform/sprd-sdhci.3/by-name/efs flags=backup=1;display=EFS
/external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/usb-otg vfat /dev/block/sda1 /dev/block/sda flags=removable;storage;display=USB-OTG
Click to expand...
Click to collapse
EDIT:
Here is some partition information from my device
Number Start End Size File system Name Flags
1 4194304B 6291455B 2097152B SBOOT msftdata
2 6291456B 8388607B 2097152B SBOOT2 msftdata
3 8388608B 9437183B 1048576B wfixnv1 msftdata
4 9437184B 10485759B 1048576B wfixnv2 msftdata
5 10485760B 11534335B 1048576B tdfixnv1 msftdata
6 11534336B 12582911B 1048576B tdfixnv2 msftdata
7 12582912B 16777215B 4194304B WDSP msftdata
8 16777216B 25165823B 8388608B MODEM msftdata
9 25165824B 33554431B 8388608B MODEM2 msftdata
10 33554432B 37748735B 4194304B TDDSP msftdata
11 37748736B 38797311B 1048576B FOTA_SIG msftdata
12 38797312B 39845887B 1048576B wruntimenv1 msftdata
13 39845888B 40894463B 1048576B wruntimenv2 msftdata
14 40894464B 41943039B 1048576B tdruntimenv1 msftdata
15 41943040B 42991615B 1048576B tdruntimenv2 msftdata
16 42991616B 45088767B 2097152B PARAM msftdata
17 45088768B 66060287B 20971520B ext4 efs msftdata
18 66060288B 71303167B 5242880B ext4 prodnv msftdata
19 71303168B 72351743B 1048576B RESERVED2 msftdata
20 72351744B 89128959B 16777216B KERNEL msftdata
21 89128960B 105906175B 16777216B RECOVERY msftdata
22 105906176B 315621375B 209715200B ext4 CSC msftdata
23 315621376B 1888485375B 1572864000B ext4 system msftdata
24 1888485376B 1901068287B 12582912B ext4 HIDDEN msftdata
25 1901068288B 7802454015B 5901385728B ext4 userdata msftdata
Click to expand...
Click to collapse
lrwxrwxrwx root root 2019-05-20 19:56 CSC -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2019-05-20 19:56 FOTA_SIG -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2019-05-20 19:56 HIDDEN -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2019-05-20 19:56 KERNEL -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2019-05-20 19:56 MODEM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2019-05-20 19:56 MODEM2 -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2019-05-20 19:56 PARAM -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2019-05-20 19:56 RECOVERY -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2019-05-20 19:56 RESERVED2 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2019-05-20 19:56 SBOOT -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2019-05-20 19:56 SBOOT2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2019-05-20 19:56 TDDSP -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2019-05-20 19:56 WDSP -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2019-05-20 19:56 efs -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2019-05-20 19:56 prodnv -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2019-05-20 19:56 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2019-05-20 19:56 tdfixnv1 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2019-05-20 19:56 tdfixnv2 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2019-05-20 19:56 tdruntimenv1 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2019-05-20 19:56 tdruntimenv2 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2019-05-20 19:56 userdata -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2019-05-20 19:56 wfixnv1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2019-05-20 19:56 wfixnv2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2019-05-20 19:56 wruntimenv1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2019-05-20 19:56 wruntimenv2 -> /dev/block/mmcblk0p13
Click to expand...
Click to collapse
Any help would be greatly appreciated!
Thanks!