[Q] Copying /userdata to sd or PC - Android Q&A, Help & Troubleshooting

[Q] Copying /userdata to sd or PC - Android Q&A, Help & Troubleshooting

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.

Related

partitions of sony tablet s

note:this is a study log,i'am not sure if blow is all right:cyclops:
Code:
major minor #blocks dev format name mount note
179 1 2048 mmcblk0p1 ext2 CF /configs
179 2 393216 mmcblk0p2 ext4 A0 /system system.img flash here
179 3 393216 mmcblk0p3 ext4 A1 /system backup system?
179 4 524288 mmcblk0p4 ext4 CC /cache
179 5 2048 mmcblk0p5 ???? MC /misc can't mount
179 6 49152 mmcblk0p6 ???? UP /staging hidden.img flash here
179 7 1024 mmcblk0p7 ???? BF /blflags can't mount
179 8 393216 mmcblk0p8 ext4 DP /datapp manel mount
179 9 16384 mmcblk0p9 ext4 LG /log
179 10 4194304 mmcblk0p10 ext4 UA /data
179 11 9368576 mmcblk0p11 vfat SC /sdcard
here mmcblk0 is first mmc-block device,that is inner storage
mmcblk0p1 is first partition of mmcblk0
block size is 1 KB,so block count 2048 means size is 2MB
there are 2 system partition(p2,p3),p2 is main system partition,if something wrong with p2,system will use p3 for backup.
my tablet first boot will stop at sony logo(use p2),2nd boot will ok(use p3)
if i flash ics,it will flash to p2,and can't use in forst boot,but after wipe,it will back to 3.2.1 again,then next boot to ics....
??system rember what system used in blflag(p7)+0xC.
(in updater-script read_index("/blflags") and code in update-binary)
if the byte is 0,use p2,else use p3,my is 1
content of p7:all zero but 0x03C -- 0x1FB is 0xFF,and
Code:
0x0C:1
0x14:1
0x1fC:0xD2A7AA14
0x1000:BL_VERSION_INFO\0
0x1010:_BL\0 0x00000008
0x1020:_RM\0 0x0000001E
0x1030:_LX\0 0x07334EFF
0x1040:_E1\0 0x00000009
a wipe data will format partition:
data,cache,log,staging
when flash rom,system.img flash to p2 or p3,hidden.img flash to p6
condi's double flash roms flash both to p2 and p3
some cmd:
get partion list
Code:
cat /proc/partitions
p3,p6,p8 is only use in update-script,but you can mout it by cmd
Code:
mount -t ext4 /dev/block/mmcblk0p3 /dir-name
p5,p7,format is unknow,mount fail,but you can dump it's data by cmd
Code:
cat /dev/block/mmcblk0p3 /some-name.bin
or
Code:
dd if=/dev/block/mmcblk0p3 of=/some-name.bin
in theory,you can restore partition by dd cmd,but it's very dangers!
you can check what system you use by cmd mount
Code:
# mount
mount
rootfs / rootfs rw,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
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/mmcblk0p1 /configs ext2 ro,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
[COLOR="Red"]/dev/block/mmcblk0p3 /system ext4 rw,relatime,barrier=1,data=ordered 0 0[/COLOR]
/dev/block/mmcblk0p10 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered
0 0
/dev/block/mmcblk0p4 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered
0 0
/dev/block/mmcblk0p9 /log ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0
0
/dev/block/svold/179:17 /mnt/sdcard2 vfat rw,dirsync,nosuid,nodev,noexec,relatim
e,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iochar
set=iso8859-1,shortname=mixed,batch_sync,utf8,comp_uni,avoid_dlink,errors=remoun
t-ro 0 0
/dev/block/vold/179:11 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,
uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharse
t=iso8859-1,shortname=mixed,batch_sync,utf8,comp_uni,avoid_dlink,errors=remount-
ro 0 0
/dev/block/vold/179:11 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,batch_sync,utf8,comp_uni,avoid_dlink,errors=rem
ount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
View attachment partitions.7z

Have anyone treis to flip this blaflags partition flag which tells which partition to reboot from? It could allow more versatile flashing...

According to Chainfire's floating performance monitor application the Disk I/O is mmcblk0.
Sent from my Nexus 4 using xda app-developers app

Where is the kernel? In the system partition, because i can´t see a boot partition in your list...

Partitionator said:
Where is the kernel? In the system partition, because i can´t see a boot partition in your list...
Click to expand...
Click to collapse
mmcblk0p6
Thats also where recovery is, hidden.img is kernel + recovery

lopezk38 said:
mmcblk0p6
Thats also where recovery is, hidden.img is kernel + recovery
Click to expand...
Click to collapse
no,no,no
in normal case mmcblk0p6 is empty
1,mount it,will get only "lost+found" dir
2,dump it by dd,it's almost 50M of zero
as it's name,mmcblk0p6 is only a staging,when update system,hidden.img(kernel + recovery) will flash to mmcblk0p6,
but after reboot,the data will be cut to some place else.maybe a hidden partition we don't know
ánd the file used in recovery is not in the list too..

;45311156 said:
no,no,no
in normal case mmcblk0p6 is empty
1,mount it,will get only "lost+found" dir
2,dump it by dd,it's almost 50M of zero
as it's name,mmcblk0p6 is only a staging,when update system,hidden.img(kernel + recovery) will flash to mmcblk0p6,
but after reboot,the data will be cut to some place else.maybe a hidden partition we don't know
ánd the file used in recovery is not in the list too..
Click to expand...
Click to collapse
Robin, we need you to join the Sony Tablet Bootloader Discussion on Google Hangouts, can you PM me with your email with the subject "STBD"?
Sent from my Nexus 4 using Tapatalk 4

[Q] Check device Mount point mapping?

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!!!

[Q] Cant Find my Recovery Partition

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.

[solved][i9100][5.1.1][CM12.1] Read only permission on extSdCard formatted with Ext4

Hello!
I have put a MicroSD card in the device that I formatted with Ext4 with my PC in advance.
On the MicroSD card I copied > 10GB of data.
The MicroSD is mounted correctly in /storage/sdcard1:
Code:
[email protected]:~$ adb shell mount
rootfs / rootfs ro,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
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
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p9 /system ext4 ro,seclabel,noatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p7 /cache ext4 rw,seclabel,nosuid,nodev,noatime,errors=panic,user_xattr,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p1 /efs ext4 rw,seclabel,nosuid,nodev,noatime,errors=panic,user_xattr,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p10 /data ext4 rw,seclabel,nosuid,nodev,noatime,errors=panic,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p12 /preload ext4 rw,seclabel,nosuid,nodev,noatime,user_xattr,barrier=1,journal_async_commit,data=ordered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/259:3 /mnt/media_rw/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/259:3 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/vold/179:9 /mnt/media_rw/sdcard1 ext4 rw,dirsync,context=u:object_r:sdcard_posix:s0,nosuid,nodev,noexec,noatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/vold/179:9 /mnt/secure/asec ext4 rw,dirsync,context=u:object_r:sdcard_posix:s0,nosuid,nodev,noexec,noatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/vold/179:9 /mnt/media_rw/sdcard0/.android_secure ext4 rw,dirsync,context=u:object_r:sdcard_posix:s0,nosuid,nodev,noexec,noatime,user_xattr,barrier=1,data=ordered 0 0
/dev/fuse /storage/sdcard1 fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
Checking the user and group permissions they are equal for /storage/sdcard0 and /storage/sdcard1:
Code:
[email protected]:~$ adb shell ls -l /storage
drwxrwx--x root sdcard_r 2015-08-08 14:33 sdcard0
drwxrwx--x root sdcard_r 2015-08-06 20:27 sdcard1
drwxrwx--- root root 2015-08-08 11:36 usbdisk0
This is also true for any file / directory stored in /storage/sdcard1:
Code:
[email protected]:~$ adb shell ls -l /storage/sdcard1
drwxrwx--x root sdcard_r 2015-03-28 16:11 Android
drwxrwx--- root sdcard_r 2015-08-05 17:41 DCIM
drwxrwx--- root sdcard_r 2015-08-06 02:13 TWRP
drwxrwx--- root sdcard_r 2015-08-05 10:34 TitaniumBackup
drwxrwx--- root sdcard_r 2015-03-28 16:11 audio
drwxrwx--- root sdcard_r 2015-08-04 17:10 backup
drwxrwx--- root sdcard_r 2015-03-28 16:12 bilder
drwxrwx--- root sdcard_r 2015-04-23 16:40 brouter
drwxrwx--- root sdcard_r 2015-05-21 14:43 clockworkmod
drwxrwx--- root sdcard_r 2015-03-28 16:17 data
drwxrwx--- root sdcard_r 2015-03-28 16:19 documents
drwxrwx--- root sdcard_r 2015-08-05 22:55 download
drwxrwx--- root sdcard_r 2015-05-31 22:02 keepass
drwxrwx--- root sdcard_r 2015-08-05 22:16 lost+found
drwxrwx--- root sdcard_r 2015-03-28 16:27 musik
drwxrwx--- root sdcard_r 2015-08-03 20:49 oruxmaps
drwxrwx--- root sdcard_r 2015-03-28 16:29 video
-rw-rw---- root sdcard_r 307873 2015-08-08 16:20 xposed-uninstaller-arm.zip
-rw-rw---- root sdcard_r 3540968 2015-08-08 16:20 xposed-v69-sdk22-arm-by-romracer-20150804.zip
However, I cannot write any file to /storage/sdcard1/<subdirectory>:
Code:
[email protected]:/storage/sdcard1 $ cp -v xposed-* backup/
cp: backup/xposed-uninstaller-arm.zip: Permission denied
cp: backup/xposed-v69-sdk22-arm-by-romracer-20150804.zip: Permission denied
Question:
Why is any subdirecty in /storage/sdcard1 with read-only permission?
THX

So, how do U solve the problem?

Porting CWM to Goclever Quantum 500 - black screen

Hey.
I would like to port CWM to Goclever Quantum 500
I use the official documentation from cyanogenmod website
Compilation goes flawlessly.
Code:
Install: /home/mazur/android/system/out/target/product/java_gfive_wg5002g/recovery/root/sbin/recovery
----- Making recovery ramdisk ------
Copying baseline ramdisk...
Modifying ramdisk contents...
cp: cannot stat '/home/mazur/android/system/out/target/product/java_gfive_wg5002g/root/init.recovery.*.rc': No such file or directory
----- Making uncompressed recovery ramdisk ------
----- Making compressed recovery ramdisk ------
----- Making recovery image ------
+/home/mazur/android/system/out/target/product/java_gfive_wg5002g/recovery.img maxsize=34197504 blocksize=135168 total=8536064 reserve=405504
Made recovery image: /home/mazur/android/system/out/target/product/java_gfive_wg5002g/recovery.img
#### make completed successfully (32:32 (mm:ss)) ####
But after flashing (flash goes flawlessly too - I tried flashify and fastboo btw) and trying entering the recovery I see only a black screen and nothing more.
Before flashing CWM I have generated stock recovery using flashify. Reflasing stock recovery works perfectly.
I have edited recovery.fstab based on recovery stock
recovery.fstab
Code:
# mount point fstype device option
/dev/block/platform/sdhci.0/mmcblk1p1 /sdcard vfat defaults wait
/dev/block/platform/sdhci.1/by-name/sdcard /sdcard0 vfat defaults wait
/dev/block/platform/sdhci.1/by-name/system /system ext4 rw wait
/dev/block/platform/sdhci.1/by-name/userdata /data ext4 rw wait,length=-16384
/dev/block/platform/sdhci.1/by-name/cache /cache ext4 rw wait
/dev/block/platform/sdhci.1/by-name/misc /misc emmc rw wait
/dev/block/platform/sdhci.1/by-name/boot /boot emmc rw wait
/dev/block/platform/sdhci.1/by-name/recovery /recovery emmc rw wait
/dev/block/platform/sdhci.1/by-name/u-boot /u-boot emmc rw wait
/dev/block/platform/sdhci.1/by-name/dt-blob /dt-blob emmc rw wait
/dev/block/platform/sdhci.1/by-name/cp-boot /cp-boot emmc rw wait
/dev/block/platform/sdhci.1/by-name/cp-image /cp-image emmc rw wait
/dev/block/platform/sdhci.1/by-name/dsp-dram /dsp-dram emmc rw wait
/dev/block/platform/sdhci.1/by-name/dsp-pram /dsp-pram emmc rw wait
/dev/block/platform/sdhci.1/by-name/sys-parm-ind /sys-parm-ind emmc rw wait
/dev/block/platform/sdhci.1/by-name/parm-spml-ind /parm-spml-ind emmc rw wait
/dev/block/platform/sdhci.1/by-name/ubootlogo /ubootlogo emmc rw wait
/dev/block/platform/sdhci.1/by-name/abi /abi emmc rw wait
/dev/block/platform/sdhci.1/by-name/abi-sec /abi-sec emmc rw wait
/dev/block/platform/sdhci.1/by-name/hwconf /hwconf emmc rw wait
/dev/block/platform/sdhci.1/by-name/loader /loader emmc rw wait
/dev/block/platform/sdhci.1/by-name/parm-spml-dep /parm-spml-dep emmc rw wait
/dev/block/platform/sdhci.1/by-name/sys-parm-dep /sys-parm-dep emmc rw wait
/dev/block/platform/sdhci.1/by-name/umts-cal /umts-cal emmc rw wait

BoardConfig.mk generated by mkvendor.sh
[..]
TARGET_ARCH := arm
TARGET_NO_BOOTLOADER := true
TARGET_BOARD_PLATFORM := unknown
TARGET_CPU_ABI := armeabi-v7a
TARGET_CPU_ABI2 := armeabi
TARGET_ARCH_VARIANT := armv7-a-neon
TARGET_CPU_VARIANT := cortex-a7
# fix this up by examining /proc/mtd on a running device
BOARD_BOOTIMAGE_PARTITION_SIZE := 16777216
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 33554432
BOARD_SYSTEMIMAGE_PARTITION_SIZE :=891289600
BOARD_USERDATAIMAGE_PARTITION_SIZE := 1614807040
BOARD_FLASH_BLOCK_SIZE := 131072
[..]

some info from adb shell:
Code:
[email protected]_gfive_wg5002g:/ # df
Filesystem Size Used Free Blksize
/dev 479.0M 128.0K 478.8M 4096
/sys/fs/cgroup 479.0M 12.0K 479.0M 4096
/mnt/secure 479.0M 0.0K 479.0M 4096
/mnt/asec 479.0M 0.0K 479.0M 4096
/mnt/asec/com.koushikdutta.rommanager-1 5.0M 3.6M 1.4M 4096
/mnt/asec/zip.me-1 6.1M 4.2M 1.9M 4096
/mnt/asec/me.kuder.diskinfo-1 3.0M 1.1M 1.9M 4096
/mnt/asec/com.cgollner.flashify-2 17.2M 14.1M 3.0M 4096
/mnt/asec/org.xbmc.kore-1 4.0M 2.9M 1.1M 4096
/mnt/asec/com.cpuid.cpu_z-1 4.0M 2.4M 1.6M 4096
/mnt/obb 479.0M 0.0K 479.0M 4096
/mnt/media_rw/sdcard0 1022.0M 686.0M 336.0M 4096
/mnt/media_rw/sdcard1 12.7G 674.4M 12.0G 4096
/storage/emulated 479.0M 0.0K 479.0M 4096
/storage/sdcard0 1022.0M 686.0M 336.0M 4096
/storage/sdcard1 12.7G 674.4M 12.0G 4096
/system 823.3M 632.6M 190.7M 4096
/cache 143.6M 232.0K 143.4M 4096
/data 1.5G 1.3G 183.1M 4096
/storage/emulated/legacy 479.0M 0.0K 479.0M 4096
Code:
rootfs / rootfs ro,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
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 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
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/block/dm-0 /mnt/asec/com.koushikdutta.rommanager-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-1 /mnt/asec/zip.me-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-2 /mnt/asec/me.kuder.diskinfo-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-3 /mnt/asec/com.cgollner.flashify-2 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-4 /mnt/asec/org.xbmc.kore-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-5 /mnt/asec/com.cpuid.cpu_z-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/media_rw tmpfs rw,seclabel,relatime,size=0k,mode=700,uid=1023,gid=1023 0 0
/dev/block/vold/179:32 /mnt/media_rw/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:169 /mnt/media_rw/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /storage tmpfs rw,seclabel,relatime,size=0k,mode=751,gid=1028 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,mode=050,gid=1028 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 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/platform/sdhci.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/sdhci.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,errors=panic,data=ordered 0 0
/dev/block/platform/sdhci.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=panic,data=ordered 0 0
tmpfs /storage/emulated/legacy tmpfs rw,seclabel,nosuid,nodev,relatime,mode=050,gid=1028 0 0
Code:
[email protected]_gfive_wg5002g:/ # ls -la /dev/block/platform/sdhci.1/by-name/
lrwxrwxrwx root root 2013-01-01 01:02 abi -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-01-01 01:02 abi-sec -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-01-01 01:02 boot -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2013-01-01 01:02 boot-parm -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-01-01 01:02 cache -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2013-01-01 01:02 cp-boot -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2013-01-01 01:02 cp-image -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2013-01-01 01:02 cp-pod -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2013-01-01 01:02 custom-cert -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2013-01-01 01:02 devinfo -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2013-01-01 01:02 dsp-dram -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2013-01-01 01:02 dsp-pram -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2013-01-01 01:02 dt-blob -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2013-01-01 01:02 hwconf -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-01-01 01:02 kpanic -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2013-01-01 01:02 loader -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-01-01 01:02 misc -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2013-01-01 01:02 mobicore -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2013-01-01 01:02 oeminfo -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2013-01-01 01:02 parm-spml-dep -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2013-01-01 01:02 parm-spml-ind -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-01-01 01:02 ramdisk-broadcom -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 2013-01-01 01:02 recovery -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2013-01-01 01:02 sdcard -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 2013-01-01 01:02 sys-parm-dep -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-01-01 01:02 sys-parm-ind -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2013-01-01 01:02 system -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2013-01-01 01:02 u-boot -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2013-01-01 01:02 u-boot-env -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2013-01-01 01:02 ubootlogo -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2013-01-01 01:02 umts-cal -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2013-01-01 01:02 userdata -> /dev/block/mmcblk0p31
Code:
[email protected]_gfive_wg5002g:/dev/block/platform/sdhci.1/by-name # for x in `ls`;do busybox fdisk -l $x;done
[....]
Disk boot: 16 MB, 16777216 bytes
4 heads, 16 sectors/track, 512 cylinders
Disk boot-parm: 0 MB, 65536 bytes
4 heads, 16 sectors/track, 2 cylinders
Disk cache: 157 MB, 157286400 bytes
4 heads, 16 sectors/track, 4800 cylinders
Disk cp-boot: 0 MB, 32768 bytes
4 heads, 16 sectors/track, 1 cylinders
Disk loader: 0 MB, 131072 bytes
4 heads, 16 sectors/track, 4 cylinders
Disk misc: 0 MB, 262144 bytes
4 heads, 16 sectors/track, 8 cylinders
Disk ramdisk-broadcom: 5 MB, 5242880 bytes
4 heads, 16 sectors/track, 160 cylinders
Disk recovery: 33 MB, 33554432 bytes
4 heads, 16 sectors/track, 1024 cylinders
Disk sdcard: 1073 MB, 1073741824 bytes
4 heads, 16 sectors/track, 32768 cylinders
Disk system: 891 MB, 891289600 bytes
4 heads, 16 sectors/track, 27200 cylinders
Disk u-boot: 1 MB, 1048576 bytes
4 heads, 16 sectors/track, 32 cylinders
Disk ubootlogo: 5 MB, 5242880 bytes
4 heads, 16 sectors/track, 160 cylinders
Disk userdata: 1614 MB, 1614807040 bytes
4 heads, 16 sectors/track, 49280 cylinders
[..]
my CWM recovery image dropbox.com/s/1r4bkppweenkmxs/recovery.img?dl=0
my Stock recovery: dropbox.com/s/imndi2fg5t9vr54/Stock%20Recovery?dl=0
Sorry for post splitting and weak link. I was unable to send one so long post and links
Can you help me solve this problem?

Better Mobile App

welcome