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!!!
Related
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.
Hello,
I have a relatively unknown phone: RIV R55 Reach Tech Xiamen.
I'd like to take a backup of at least /system /data prior to rooting using TWRP. I'm just not clear how to customize TWRP for the phone, basically how to map the partitions and change resolution. I think I can start from a Nexus 5 TWRP image and work from there. Can I simply mount the IMG and back the necessary changes to backup / restore? Or must I compile TWRP from scratch?
I was able to pull of some info: cat /proc/mounts
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
debugfs /mnt/debugfs debugfs rw,relatime,gid=512 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.3/by-num/p17 /system ext4 ro,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.3/by-num/p21 /data ext4 rw,nosuid,nodev,relatime,nomblk_io_submit,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/platform/msm_sdcc.3/by-num/p18 /cache ext4 rw,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.3/by-num/p15 /persist ext4 rw,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/vold/179:20 /storage/sdcard0 vfat rw,nosuid,nodev,noexec,noatime,nodiratime,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:20 /mnt/secure/asec vfat rw,nosuid,nodev,noexec,noatime,nodiratime,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:33 /storage/sdcard1 vfat rw,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1023,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
ls /dev/block/platform/msm_sdcc.1
Code:
lrwxrwxrwx root root 2015-02-02 10:57 mmcblk1 -> /dev/block/mmcblk1
lrwxrwxrwx root root 2015-02-02 10:57 mmcblk1p1 -> /dev/block/mmcblk1p1
ls /dev/block/platform/msm_sdcc.3
Code:
drwxr-xr-x root root 2015-02-02 10:57 by-num
lrwxrwxrwx root root 2015-02-02 10:57 mmcblk0 -> /dev/block/mmcblk0
lrwxrwxrwx root root 2015-02-02 10:57 mmcblk0p1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-02-02 10:57 mmcblk0p10 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-02-02 10:57 mmcblk0p11 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-02-02 10:57 mmcblk0p12 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-02-02 10:57 mmcblk0p13 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-02-02 10:57 mmcblk0p14 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-02-02 10:57 mmcblk0p15 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-02-02 10:57 mmcblk0p16 -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-02-02 10:57 mmcblk0p17 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-02-02 10:57 mmcblk0p18 -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-02-02 10:57 mmcblk0p19 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-02-02 10:57 mmcblk0p2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-02-02 10:57 mmcblk0p20 -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-02-02 10:57 mmcblk0p21 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-02-02 10:57 mmcblk0p22 -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2015-02-02 10:57 mmcblk0p23 -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2015-02-02 10:57 mmcblk0p3 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-02-02 10:57 mmcblk0p4 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-02-02 10:57 mmcblk0p5 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-02-02 10:57 mmcblk0p6 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-02-02 10:57 mmcblk0p7 -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-02-02 10:57 mmcblk0p8 -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-02-02 10:57 mmcblk0p9 -> /dev/block/mmcblk0p9
Any help would be greatly appreciated. Thanks
EDIT: I'm able to extract a twrp nexus 5 base image. Can I just alter the fstab.hammerhead inside initrd.img file for my /system and /data partitions?
Thoughts?
I have the same question as you, were you able to find the answer? or how to root RIW Android 4.4.2?
I worked on this last year, hoping to have a proper TWRP build created. Instead, I've had no time, and just hacked up the Nexus 5 recovery image instead and integrated a skin with the right resolution. This only works with the v1 as far as I'm aware, but may work on v2 if they use the same partition layout.
I would recommend you test it first before flashing it.
To test:
1. Shut off phone
2. Hold down volume up + power until the Linux logo appears
3. Plug in to USB cable
4. Run: fastboot boot riv-r55-v1.img
5. Wait aboue 20-30 seconds until TWRP appears
I have attached riv-r55-v1.img as a .tar file..make sure to untar it first!
Works
- Backup and restore to bootable state
- MTP connection to transfer files
- Most things
Known Issues
- Reboot doesn't work most of the time, you have to take out the battery instead
- Some fonts too big and not readable, can view recovery.log to view it via ADB instead
- Can only backup to fixed location
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download View attachment riv-r55-v1.tar
Hopefully someone can port Cyanogenmod to this device. However, I am very skeptical, as they have ignored my GPL code requests (they have modified kernel modules that have the company name in them).
Q & A
Q: Where is the backup saveD?
A: Data is saved in /data/media/TWRP/
Q: Can i use this to install a root installer
A: Yes, you can install supersu, etc, as long as they have a flashable zip
CREDITS:
- Theme: http://forum.xda-developers.com/nexus-4/themes-apps/theme-twrp-holofied-black-dark-light-t2396687
- TWRP for Nexus 5 team
I would like to copy a block that contains userdata to SD or a PC.
The author of undelete suggested to use:
adb shell su cat /dev/block/platform/msm_sdcc.1/by-name/userdata > /home/data_image.dat
I connected my phone to a PC and wrote in powercmd:
adb shell
su
cat /dev/block/mmcblk1p1 > /home/data_image.dat
sh: can't create /home/data_image.dat: No such file or directory
What am I doing wrong?
The second question is how to find out what block contains userdata? I just guessed it might be in mmcblk1p1.
When I write "mount" I get:
mount
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/secure tmpfs rw,relatime,mode=700 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,noatime,noauto_da_alloc,commit=1,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
/[email protected]_f /protect_f ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected]_s /protect_s ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/dev/fuse /storage/sdcard1 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 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/dm-0 /mnt/asec/com.outfit7.talkingtom2free-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-1 /mnt/asec/com.skype.raider-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-2 /mnt/asec/com.VAMflax.ChopperMike-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
I tried going into this dir and ls -al it:
[email protected]:/dev/block/platform # ls -al
ls -al
drwxr-xr-x root root 2015-07-08 11:57 mtk-msdc.1
[email protected]:/dev/block/platform/mtk-msdc.1 # ls -al
ls -al
lrwxrwxrwx root root 2015-07-08 11:57 mmcblk1 -> /dev/block/mmcblk1
lrwxrwxrwx root root 2015-07-08 11:57 mmcblk1p1 -> /dev/block/mmcblk1p1
For some reason mtk-msdc.0 is not visible via ls -al!? But I can cd to it:
[email protected]:/dev/block/platform/mtk-msdc.0 # ls -al
ls -al
lrwxrwxrwx root root 2015-07-08 11:57 mmcblk0 -> /dev/block/mmcblk0
lrwxrwxrwx root root 2015-07-08 11:57 mmcblk0boot0 -> /dev/block/mmcblk0boot0
lrwxrwxrwx root root 2015-07-08 11:57 mmcblk0boot1 -> /dev/block/mmcblk0boot1
lrwxrwxrwx root root 2015-07-08 11:57 mmcblk0p1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-07-08 11:57 mmcblk0p2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-07-08 11:57 mmcblk0p3 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-07-08 11:57 mmcblk0p4 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-07-08 11:57 mmcblk0p5 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-07-08 11:57 mmcblk0p6 -> /dev/block/mmcblk0p6
So, according to https://blog.avast.com/2014/07/09/android-foreniscs-pt-2-how-we-recovered-erased-data/ that uses "mount" to discover the block for userdata, my userdata is located at /[email protected] But I'm not sure how can I access this directory.
Another thing I don't understand:
[email protected]:/dev/block/platform/mtk-msdc.1 $ ls -al
ls -al
drwxr-xr-x root root 2015-07-08 11:57 by-num
lrwxrwxrwx root root 2015-07-08 11:57 mmcblk1 -> /dev/block/mmcblk1
lrwxrwxrwx root root 2015-07-08 11:57 mmcblk1p1 -> /dev/block/mmcblk1p1
[email protected]:/dev/block/platform/mtk-msdc.1 $ su
su
[email protected]:/dev/block/platform/mtk-msdc.1 # ls -al
ls -al
lrwxrwxrwx root root 2015-07-08 11:57 mmcblk1 -> /dev/block/mmcblk1
lrwxrwxrwx root root 2015-07-08 11:57 mmcblk1p1 -> /dev/block/mmcblk1p1
[email protected]:/dev/block/platform/mtk-msdc.1 #
As you can see, my phone ACER Z130 uses "by-num" instead of "by-name" for some reason.
I also wonder why after su I cannot see this dir in ls -l.
Also, some more tries:
D:\Program Files\PowerCmd>adb shell su cat /dev/block/mmcblk1p1 > /home/data.img
The system cannot find the path specified.
D:\Program Files\PowerCmd>adb shell su cat /dev/block/mmcblk1p1 > /data.img
sh: /dev/block/mmcblk1p1: can't execute: Permission denied
So, after reading for hours about how to do that, I'm still stuck.
Also, note, that it seems that on my phone internal mem and sdcard might be reversed in order. At least File Manager shows that sdcard0 has the content of the sd, and sdcard1 has the content of internal memory.
Ok, I did:
2|[email protected]:/ # ls -al
lrwxrwxrwx root root 1970-01-01 07:00 [email protected] -> /dev/block/mmcblk0p6
Ok, found that userdata.
cat /proc/partitions
179 6 2585728 mmcblk0p6
df
/dev 236M 52K 236M 4096
/mnt/secure 236M 0K 236M 4096
/mnt/asec 236M 0K 236M 4096
/mnt/obb 236M 0K 236M 4096
/system 756M 632M 124M 4096
/data 2G 1G 488M 4096
/cache 251M 4M 246M 4096
/protect_f 8M 4M 4M 4096
/protect_s 8M 4M 4M 4096
/storage/sdcard1 2G 1G 438M 4096
/storage/sdcard0 3G 3G 539M 32768
And:
Filesystem volume name: <none>
Last mounted on: /data
Filesystem UUID: 57f8f4bc-abf4-655f-bf67-946fc0f9f25b
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal resize_inode filetype needs_recovery extent sparse_super large_file
Filesystem flags: unsigned_directory_hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Remount read-only
Filesystem OS type: Linux
Inode count: 163840
Block count: 646176
Reserved block count: 0
Free blocks: 115667
Free inodes: 157106
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 95
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8192
Inode blocks per group: 512
Last mount time: Wed Jul 8 11:57:16 2015
Last write time: Wed Jul 8 11:57:16 2015
Mount count: 1
Maximum mount count: -1
Last checked: Wed Jul 8 11:57:10 2015
Check interval: 0 (<none>)
Lifetime writes: 95 GB
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode: 8
First orphan inode: 131321
Default directory hash: tea
Journal backup: inode blocks
So, I assume the size of the block is about 2.5GB?
Ok, so how can I copy it now to my PC (preferable) or to SD?
dd if=/dev/block/mmcblk0p6 bs=4194304 of=/storage/sdcard0/data.img
adb pull /storage/sdcard0/data.img /Users/????/Desktop/data.img
or try this (i dont know if it will work)
adb shell su -c 'cat /dev/block/mmcblk0p6' > /Users/????/Desktop/data.img
if that doesn't work try this
adb shell 'su -c 'cat /dev/block/mmcblk0p6'' > /Users/????/Desktop/data.img
you need admin rights to write data.img in C:\ , so put your desktop folder.
Ok,
I managed to do that. Now I have the image and I would like to recover the deleted/corrupted contacts2.db file. Any suggestions how to do that?
Blackion said:
Ok,
I managed to do that. Now I have the image and I would like to recover the deleted/corrupted contacts2.db file. Any suggestions how to do that?
Click to expand...
Click to collapse
Boot into linux and mount the image,
Code:
[email protected] ~ # mount /path/to/data.img /mnt
[email protected] ~ # cd /mnt
[email protected] /mnt # nautilus .
Also please quote me or mention me if you're replying to me, I don't get a notification if you don't do it.
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!
Please Help!!!
First off, I openly admit to my newbness. I've had a little experience reflashing a tablet once but not much beyond that since I've had an Apple for about the past 5 years. I'm an IT admin with a background ranging from desktops to servers and going back as far as early dos versions so plenty of hardware/software/cli experience and understanding.
I picked up a soft bricked ZTE Z987, thinking it would be easy enough to reload the stock rom and go about my day. My previous tablet experience had gone well, this should be similar, right? Wrong...so far, anyways. I don't know how this device got into the state it is currently in, Ebay purchase. I can only assume the previous owner attempted to flash an incorrect rom and hosed it all up. The stock recovery, or any other recovery, appears to be missing and the phone is in what I guess would be considered a bootloop.
The Max X + splash screen shows up for a few seconds then the screen goes black although you can see it slight lit up in the dark. It will sit like that all day long.
Vol dn + pwr will go into FTM mode.
Both vol keys + pwr and goes into DFU mode.
Vol up + pwr gives the splash screen then black instead of recovery.
When connected to my pc and in FTM mode, adb can see it as ? device, yes the name of the device is question mark. I was able to successfully copy a file using adb. adb -sideload recovery.img responds with error: closed.
That's all the further I have gotten so far. What now? I have Masterchief's stock rom replacement file and I have the 5.1 update downloaded from ZTE site. I'd prefer to do the stock 4.4.4 rom first so I can root it before upgrading but first things first, I need to load a recovery manager somehow.
Thank you to the mod who moved me to the correct section!
I've been poking through more threads today and found some additional adb commands that allow me to list the contents of the phones file system (telling you smart guys what you already know). I am assuming that through this, I would be able to locate the faulty recovery partition and replace it with one from the stock rom, correct? Once recovery is fixed, I should have no problem reflashing. The recovery.img and the boot.img in the stock rom are both 16384k. There are 3 partitions with that size. listed on the phone. What the heck is the 3rd one?
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
? device
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
[email protected]:/ $ su
[email protected]:/ # cat /proc/partitions
major minor #blocks name
253 0 196608 zram0
179 0 15388672 mmcblk0
179 1 8192 mmcblk0p1
179 2 8192 mmcblk0p2
179 3 8192 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 8192 mmcblk0p7
179 8 8192 mmcblk0p8
179 9 8192 mmcblk0p9
179 10 8192 mmcblk0p10
179 11 40960 mmcblk0p11
179 12 8192 mmcblk0p12
179 13 8192 mmcblk0p13
179 14 8192 mmcblk0p14
179 15 8192 mmcblk0p15
179 16 8192 mmcblk0p16
179 17 8192 mmcblk0p17
179 18 8192 mmcblk0p18
179 19 8192 mmcblk0p19
179 20 131072 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 16384 mmcblk0p22
179 23 16384 mmcblk0p23
179 24 8192 mmcblk0p24
179 25 819200 mmcblk0p25
179 26 1572864 mmcblk0p26
179 27 12435456 mmcblk0p27
179 32 512 mmcblk0rpmb
179 64 7761920 mmcblk1
179 65 7760896 mmcblk1p1
[email protected]:/ #
Anyone have suggestions on how to proceed? I'm sure this part isn't ZTE specific. Hopefully someone with some adb experience can chime in.
This forum moves fast. I hate bumping my own threads but it looks like things can get lost pretty quick around here.
ewentling said:
Anyone have suggestions on how to proceed? I'm sure this part isn't ZTE specific. Hopefully someone with some adb experience can chime in.
This forum moves fast. I hate bumping my own threads but it looks like things can get lost pretty quick around here.
Click to expand...
Click to collapse
Well, you have a lot of partitions...
Do you know what each of those partitions are?
Sent from my SGH-M919 using XDA Free mobile app
I was able to get a list of them with names yesterday. Let me see if I can figure out how I did it again and I'll post them up here.
Got it...
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
? device
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
[email protected]:/ $ su
su
[email protected]:/ # mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=952532k,nr_inodes=181098,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,size=952532k,nr_inodes=181098,mode=750,gid=1000 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,size=952532k,nr_inodes=181098,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,size=952532k,nr_inodes=181098,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,size=952532k,nr_inodes=181098,mode=755,gid=1000 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,sho
rtname=lower,errors=remount-ro 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/userdata /data ext4 rw,seclabel,nosuid,nodev,relatime,noauto_da_alloc,resuid=1000,resgid=9997,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
[email protected]:/ #
[email protected]:/ # ls -al /dev/block/platform/msm_sdcc.1/by-name
ls -al /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root root 1970-01-05 18:18 DDR -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-05 18:18 aboot -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-05 18:18 abootbak -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-05 18:18 boot -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-05 18:18 cache -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-05 18:18 fsc -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-05 18:18 fsg -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-05 18:18 misc -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-05 18:18 modem -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-05 18:18 modemst1 -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-05 18:18 modemst2 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-05 18:18 pad -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-05 18:18 persist -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-05 18:18 recovery -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-05 18:18 rpm -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-05 18:18 rpmbak -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-05 18:18 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-05 18:18 sbl1bak -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-05 18:18 sdi -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-05 18:18 splash -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-05 18:18 ssd -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-05 18:18 system -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-05 18:18 tz -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-05 18:18 tzbak -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-05 18:18 userdata -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-05 18:18 ztecfg -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-05 18:18 ztelk -> /dev/block/mmcblk0p9
[email protected]:/ #
ewentling said:
Got it...
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
? device
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
[email protected]:/ $ su
su
[email protected]:/ # mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=952532k,nr_inodes=181098,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,size=952532k,nr_inodes=181098,mode=750,gid=1000 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,size=952532k,nr_inodes=181098,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,size=952532k,nr_inodes=181098,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,size=952532k,nr_inodes=181098,mode=755,gid=1000 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,sho
rtname=lower,errors=remount-ro 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/userdata /data ext4 rw,seclabel,nosuid,nodev,relatime,noauto_da_alloc,resuid=1000,resgid=9997,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
[email protected]:/ #
[email protected]:/ # ls -al /dev/block/platform/msm_sdcc.1/by-name
ls -al /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root root 1970-01-05 18:18 DDR -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-05 18:18 aboot -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-05 18:18 abootbak -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-05 18:18 boot -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-05 18:18 cache -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-05 18:18 fsc -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-05 18:18 fsg -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-05 18:18 misc -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-05 18:18 modem -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-05 18:18 modemst1 -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-05 18:18 modemst2 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-05 18:18 pad -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-05 18:18 persist -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-05 18:18 recovery -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-05 18:18 rpm -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-05 18:18 rpmbak -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-05 18:18 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-05 18:18 sbl1bak -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-05 18:18 sdi -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-05 18:18 splash -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-05 18:18 ssd -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-05 18:18 system -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-05 18:18 tz -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-05 18:18 tzbak -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-05 18:18 userdata -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-05 18:18 ztecfg -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-05 18:18 ztelk -> /dev/block/mmcblk0p9
[email protected]:/ #
Click to expand...
Click to collapse
Make a copy of the recovery using the dd command. Then we can see if it got corrupted somehow.
Qiangong2
Sent from my RIM Q5 using XDA Free mobile app
Recovery.img is in the attached rar
I can guarantee that the recovery I attached is corrupted since the phone won't boot into it. I have a stock recovery.img though. Is there a way to overwrite the contents of that folder with the contents of the good img file? I've been getting write permission errors when I attempt to do anything
ewentling said:
I can guarantee that the recovery I attached is corrupted since the phone won't boot into it. I have a stock recovery.img though. Is there a way to overwrite the contents of that folder with the contents of the good img file? I've been getting write permission errors when I attempt to do anything
Click to expand...
Click to collapse
You've been doing it as su over adb shell right?
Sent from my Q5 using XDA Free mobile app
Qiangong2 said:
You've been doing it as su over adb shell right?
Sent from my Q5 using XDA Free mobile app
Click to expand...
Click to collapse
Yes sir.
ewentling said:
Yes sir.
Click to expand...
Click to collapse
Okay, does your phone support flashboot?
Sent from my Q5 using XDA Free mobile app
Qiangong2 said:
Okay, does your phone support flashboot?
Sent from my Q5 using XDA Free mobile app
Click to expand...
Click to collapse
flashboot doesn't see any devices. I have tried switching the phone between DFU and FTM and neither are visible to fastboot. ADB only sees the phone when it is in FTM mode.
ewentling said:
flashboot doesn't see any devices. I have tried switching the phone between DFU and FTM and neither are visible to fastboot. ADB only sees the phone when it is in FTM mode.
Click to expand...
Click to collapse
Have you tried remounting the filesystem?
Sent from my Q5 using XDA Free mobile app
Qiangong2 said:
Have you tried remounting the filesystem?
Sent from my Q5 using XDA Free mobile app
Click to expand...
Click to collapse
Could you suggest a command for that? Everything I have ran so far has been scraped together from about 100 different forum posts so I don't remember if I have tried that or not.
ewentling said:
Could you suggest a command for that? Everything I have ran so far has been scraped together from about 100 different forum posts so I don't remember if I have tried that or not.
Click to expand...
Click to collapse
A "mount" command should work
Sent from my Q5 using XDA Free mobile app
zte z987 bootloop issues
Can some one help me pls I do admit I am a noob so I've only rooted one phone before and it worked so I tried my zte. I tried like three times and it kept saying unrootable and the next time I use king root and got to 30% and shut off and is stuck in boot loop. And I don't have a computer just a working rooted device and I have no idea how to fix it. Someone please help
what if your usb debugging is off?\
i bricked my Z987 about 5-6 months ago and usb debugging wasnt on so ive been trying my ass off to get the recovery or anything to the device but driver is wrong or something. Ive put it into every mode you can think of to no avail....
guys need help
my Z987 always bootloop no recovery only FTM and DFU mode
I mistakenly flashed wrong stoks recovery
how flash orig recovery or twrp?? need this files