Hey guys.
I am currently working on making my app "kTool" compatible with the SGS3 (see here and here), for the intl. version I9300 it already works fine, but there seem to be quite some differences on the i747....
I am missing some details on partitions used on the i747.
I already found the EFS partition (mmcblk0p11), but I'm missing the partitions for kernel, recovery, modem FW and PARAM block.
If anyone know those, please do tell
And/Or I could really use the output of the following two commands on a terminal/shell:
Code:
su
ls -al /dev/block/platform/dw_mmc/by-name
ls -al /efs
Thanks
Pm sent
Sent from my SGH-I747M using Tapatalk 2
Here you go....
Code:
[email protected]:/ $ su
su
[email protected]:/ # ls -al /dev/block/platform/dw_mmc/by-name
ls -al /dev/block/platform/dw_mmc/by-name
/dev/block/platform/dw_mmc/by-name: No such file or directory
1|[email protected]:/ # ls -al /efs
ls -al /efs
drwxrwxr-x root root 1969-12-31 19:00 .files
drwxrwxr-x system system 2011-12-31 19:02 FactoryApp
drwxr-xr-x radio radio 2011-12-31 23:06 bluetooth
drwxrwxr-x system system 2011-12-31 19:00 drm
drwxrwxr-x radio radio 2011-12-31 19:02 imei
-rw-r--r-- radio radio 880 2011-12-31 19:01 redata.bin
drwxrwxr-x root root 1969-12-31 19:00 sensors
drwxrwxr-x system system 1969-12-31 19:00 wifi
-rw-r--r-- radio radio 144 2011-12-31 23:06 wv.keys
[email protected]:/ #
Thanks!
There seems to be even more different than I was already afraid it'd be....
Some folks on the Sprint side posted some info as well, and yes, there seem to be several differences compared to the international version.
http://forum.xda-developers.com/showthread.php?t=1732154
Thank you!
I am slowly gathering all required information to make it work on those models.
Another thing that confuses me is the lack of "nv_data.bin" in the /efs folder.... So the standing question is: Is backing up that folder and dumping the partition it's mounted from really enough? Or would other locations needed to be backed up as well to have the IMEI saved?
HellcatDroid said:
Thank you!
I am slowly gathering all required information to make it work on those models.
Another thing that confuses me is the lack of "nv_data.bin" in the /efs folder.... So the standing question is: Is backing up that folder and dumping the partition it's mounted from really enough? Or would other locations needed to be backed up as well to have the IMEI saved?
Click to expand...
Click to collapse
You may want to get together with zeesubalpha, he's working with IMEI stuff in this thread.
Thank you for your work on this.
dasfiend said:
You may want to get together with zeesubalpha, he's working with IMEI stuff in this thread.
Thank you for your work on this.
Click to expand...
Click to collapse
Ahh, very interesting, I shall get in touch with that development!
*runns-to-post-in-that-thread*
Any progress hellcat?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
justinblaine23 said:
Any progress hellcat?
Click to expand...
Click to collapse
Yah, but in the wrong direction - backing up the EFS partition seems no longer to be the way to back up that sensitive data holding the IMEI and stuff: http://forum.xda-developers.com/showpost.php?p=28677774&postcount=51
by-name
think this is what you were looking for:
Code:
lrwxrwxrwx 1 0 0 20 Jan 7 1970 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 0 0 21 Jan 7 1970 backup -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 0 0 20 Jan 7 1970 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 0 0 21 Jan 7 1970 cache -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 0 0 21 Jan 7 1970 efs -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 0 0 21 Jan 7 1970 fota -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 0 0 21 Jan 7 1970 fsg -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 0 0 21 Jan 7 1970 grow -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 0 0 20 Jan 7 1970 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 0 0 21 Jan 7 1970 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 0 0 21 Jan 7 1970 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 0 0 20 Jan 7 1970 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 0 0 21 Jan 7 1970 param -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 0 0 21 Jan 7 1970 persist -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 0 0 21 Jan 7 1970 recovery -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 0 0 20 Jan 7 1970 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 0 0 20 Jan 7 1970 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 0 0 20 Jan 7 1970 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 0 0 20 Jan 7 1970 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 0 0 21 Jan 7 1970 ssd -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 0 0 21 Jan 7 1970 system -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 0 0 20 Jan 7 1970 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 0 0 21 Jan 7 1970 userdata -> /dev/block/mmcblk0p15
also did a quick backup:
remove the echo and make sure you have a big sdcard.... i found a 64gb class 10 on amazon for about $90...
Code:
echo dd if=/dev/block/mmcblk0p5 of=/mnt/extSdCard/backup/good/mmcblk0p5_about.img bs=4096
echo dd if=/dev/block/mmcblk0p20 of=/mnt/extSdCard/backup/good/mmcblk0p20_backup.img bs=4096
echo dd if=/dev/block/mmcblk0p7 of=/mnt/extSdCard/backup/good/mmcblk0p7_boot.img bs=4096
echo dd if=/dev/block/mmcblk0p17 of=/mnt/extSdCard/backup/good/mmcblk0p17_cache.img bs=4096
echo dd if=/dev/block/mmcblk0p11 of=/mnt/extSdCard/backup/good/mmcblk0p11_efs.img bs=4096
echo dd if=/dev/block/mmcblk0p19 of=/mnt/extSdCard/backup/good/mmcblk0p19_fota.img bs=4096
echo dd if=/dev/block/mmcblk0p21 of=/mnt/extSdCard/backup/good/mmcblk0p21_fsg.img bs=4096
echo dd if=/dev/block/mmcblk0p23 of=/mnt/extSdCard/backup/good/mmcblk0p23_grow.img bs=4096
echo dd if=/dev/block/mmcblk0p1 of=/mnt/extSdCard/backup/good/mmcblk0p1_modem.img bs=4096
echo dd if=/dev/block/mmcblk0p12 of=/mnt/extSdCard/backup/good/mmcblk0p12_modemst1.img bs=4096
echo dd if=/dev/block/mmcblk0p13 of=/mnt/extSdCard/backup/good/mmcblk0p13_modemst2.img bs=4096
echo dd if=/dev/block/mmcblk0p9 of=/mnt/extSdCard/backup/good/mmcblk0p9_pad.img bs=4096
echo dd if=/dev/block/mmcblk0p10 of=/mnt/extSdCard/backup/good/mmcblk0p10_param.img bs=4096
echo dd if=/dev/block/mmcblk0p16 of=/mnt/extSdCard/backup/good/mmcblk0p16_persist.img bs=4096
echo dd if=/dev/block/mmcblk0p18 of=/mnt/extSdCard/backup/good/mmcblk0p18_recovery.img bs=4096
echo dd if=/dev/block/mmcblk0p6 of=/mnt/extSdCard/backup/good/mmcblk0p6_rpm.img bs=4096
echo dd if=/dev/block/mmcblk0p2 of=/mnt/extSdCard/backup/good/mmcblk0p2_sbl1.img bs=4096
echo dd if=/dev/block/mmcblk0p3 of=/mnt/extSdCard/backup/good/mmcblk0p3_sbl2.img bs=4096
echo dd if=/dev/block/mmcblk0p4 of=/mnt/extSdCard/backup/good/mmcblk0p4_sbl3.img bs=4096
echo dd if=/dev/block/mmcblk0p22 of=/mnt/extSdCard/backup/good/mmcblk0p22_ssd.img bs=4096
echo dd if=/dev/block/mmcblk0p14 of=/mnt/extSdCard/backup/good/mmcblk0p14_system.img bs=4096
echo dd if=/dev/block/mmcblk0p8 of=/mnt/extSdCard/backup/good/mmcblk0p8_tz.img bs=4096
echo dd if=/dev/block/mmcblk0p15 of=/mnt/extSdCard/backup/good/mmcblk0p15_userdata.img bs=4096
cheers... hit thanks if this helped.
Well, there are a lot of partitions on the device that are not necessarily visible all the time.
Code:
major minor #blocks name
179 0 15388672 mmcblk0
179 1 61440 mmcblk0p1
179 2 128 mmcblk0p2
179 3 256 mmcblk0p3
179 4 512 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 512 mmcblk0p6
179 7 10240 mmcblk0p7
179 8 512 mmcblk0p8
179 9 512 mmcblk0p9
179 10 10240 mmcblk0p10
179 11 13952 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 3072 mmcblk0p13
179 14 1536000 mmcblk0p14
179 15 12832768 mmcblk0p15
179 16 8192 mmcblk0p16
179 17 860160 mmcblk0p17
179 18 10240 mmcblk0p18
179 19 10240 mmcblk0p19
179 20 6144 mmcblk0p20
179 21 3072 mmcblk0p21
179 22 8 mmcblk0p22
179 23 5120 mmcblk0p23
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
c0ns0le said:
also did a quick backup:
remove the echo and make sure you have a big sdcard.... i found a 64gb class 10 on amazon for about $90...
Code:
echo dd if=/dev/block/mmcblk0p5 of=/mnt/extSdCard/backup/good/mmcblk0p5_about.img bs=4096
echo dd if=/dev/block/mmcblk0p20 of=/mnt/extSdCard/backup/good/mmcblk0p20_backup.img bs=4096
echo dd if=/dev/block/mmcblk0p7 of=/mnt/extSdCard/backup/good/mmcblk0p7_boot.img bs=4096
echo dd if=/dev/block/mmcblk0p17 of=/mnt/extSdCard/backup/good/mmcblk0p17_cache.img bs=4096
echo dd if=/dev/block/mmcblk0p11 of=/mnt/extSdCard/backup/good/mmcblk0p11_efs.img bs=4096
echo dd if=/dev/block/mmcblk0p19 of=/mnt/extSdCard/backup/good/mmcblk0p19_fota.img bs=4096
echo dd if=/dev/block/mmcblk0p21 of=/mnt/extSdCard/backup/good/mmcblk0p21_fsg.img bs=4096
echo dd if=/dev/block/mmcblk0p23 of=/mnt/extSdCard/backup/good/mmcblk0p23_grow.img bs=4096
echo dd if=/dev/block/mmcblk0p1 of=/mnt/extSdCard/backup/good/mmcblk0p1_modem.img bs=4096
echo dd if=/dev/block/mmcblk0p12 of=/mnt/extSdCard/backup/good/mmcblk0p12_modemst1.img bs=4096
echo dd if=/dev/block/mmcblk0p13 of=/mnt/extSdCard/backup/good/mmcblk0p13_modemst2.img bs=4096
echo dd if=/dev/block/mmcblk0p9 of=/mnt/extSdCard/backup/good/mmcblk0p9_pad.img bs=4096
echo dd if=/dev/block/mmcblk0p10 of=/mnt/extSdCard/backup/good/mmcblk0p10_param.img bs=4096
echo dd if=/dev/block/mmcblk0p16 of=/mnt/extSdCard/backup/good/mmcblk0p16_persist.img bs=4096
echo dd if=/dev/block/mmcblk0p18 of=/mnt/extSdCard/backup/good/mmcblk0p18_recovery.img bs=4096
echo dd if=/dev/block/mmcblk0p6 of=/mnt/extSdCard/backup/good/mmcblk0p6_rpm.img bs=4096
echo dd if=/dev/block/mmcblk0p2 of=/mnt/extSdCard/backup/good/mmcblk0p2_sbl1.img bs=4096
echo dd if=/dev/block/mmcblk0p3 of=/mnt/extSdCard/backup/good/mmcblk0p3_sbl2.img bs=4096
echo dd if=/dev/block/mmcblk0p4 of=/mnt/extSdCard/backup/good/mmcblk0p4_sbl3.img bs=4096
echo dd if=/dev/block/mmcblk0p22 of=/mnt/extSdCard/backup/good/mmcblk0p22_ssd.img bs=4096
echo dd if=/dev/block/mmcblk0p14 of=/mnt/extSdCard/backup/good/mmcblk0p14_system.img bs=4096
echo dd if=/dev/block/mmcblk0p8 of=/mnt/extSdCard/backup/good/mmcblk0p8_tz.img bs=4096
echo dd if=/dev/block/mmcblk0p15 of=/mnt/extSdCard/backup/good/mmcblk0p15_userdata.img bs=4096
Click to expand...
Click to collapse
For anyone who needs to dump the /dev/block/ images, but doesn't have a big external SD card, here's a neat trick.
I wanted a dump of mmcblk0p15 (userdata), but only have a 16gb external card. So, I used this command:
Code:
dd if=/dev/block/mmcblk0p15 bs=4096 | gzip -c > /mnt/extSdCard/userdata.img.gz
This piped the dd dump into gzip, which in turn compressed the image. So, what would have been a little over 12gb ended up being a little over 41mb.
To extract the image in Cygwin or in Linux after using adb to pull the file to a PC:
Code:
gunzip -c userdata.img.gz > userdata.img
That tiny file that had been compressed to around 41mb extracted to a little over 12gb! Just a tip for anyone who doesn't want to purchase a bigger sdcard just to make a backup.
This is how I got my data from my GT-I9192 with TWRP and CM13. I don't know if it works for the other GT-I91XX models or with other firmware, but if you are in a similar situation like me it is worth a try.
Background:
I installed Cyanogenmod 13 and TWRP successfully about two month ago.
About a week ago my phone suddenly was black and did not want to boot at all. I convinced it to restart after pulling battery/recharge cable some times and putting them back, sometimes whilest holding power button pressed at the same time, until it gave a life sign again.
Current situation:
My phone stucks at samsung logo splash screen and reboots.
When trying to boot into recovery (TWRP; VOL.UP+HOME(+POWER)) the TeamWinRecovery logo screen is shown but then reboots.
Download mode (VOL.DOWN+HOME) works, Odin recognizes phone, but flashing TWRP successfully again does not fix anything.
Fastboot and adb do not recognize phone while it is in boot loop/recovery start loop/download mode!
But the interesting part is:
I am able to get via adb shell onto the phone while it is offline! Pull battery, put it back again, connect the phone via USB to PC and leave it off. Battery charging screen shows up and about a minute later adb shell is possible. It is in a strange state then, neither sdcard nor any else partition besides system is mounted, but mounting sdcard and data partition manually is possible.
Required:
Installed Samsung drivers, downloaded ADB tools, CM13(?), root enabled for adb.
make sure phone is off (pull battery/cable, put it back again)
connect phone via usb to pc
at pc cmd type
Code:
adb wait-for-device
when prompt is back, type
Code:
adb shell
use the commands below to get to your data
list internal partitions by name:
Code:
ls -l /dev/block/platform/msm_sdcc.1/by-name
output:
Code:
total 0
lrwxrwxrwx 1 root root 20 1970-01-01 00:00 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 backup -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 boot -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 cache -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 efs -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 fota -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 fsg -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 hidden -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 20 1970-01-01 00:00 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 1970-01-01 00:00 pad -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 1970-01-01 00:00 param -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 persdata -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 persist -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 recovery -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 20 1970-01-01 00:00 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 1970-01-01 00:00 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 1970-01-01 00:00 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 1970-01-01 00:00 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 ssd -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 system -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 20 1970-01-01 00:00 tz -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 userdata -> /dev/block/mmcblk0p24 [COLOR="red"]<<< there is your userdata[/COLOR]
list all partitions with size:
Code:
cat /proc/partitions
output:
Code:
major minor #blocks name
179 0 7634944 mmcblk0
179 1 61440 mmcblk0p1
179 2 128 mmcblk0p2
179 3 256 mmcblk0p3
179 4 512 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 12800 mmcblk0p8
179 9 8192 mmcblk0p9
179 10 13952 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 10240 mmcblk0p13
179 14 10240 mmcblk0p14
179 15 10240 mmcblk0p15
179 16 7160 mmcblk0p16
179 17 3072 mmcblk0p17
179 18 8 mmcblk0p18
179 19 8192 mmcblk0p19
179 20 12288 mmcblk0p20
179 21 1536000 mmcblk0p21
179 22 204800 mmcblk0p22
179 23 36864 mmcblk0p23
179 24 5685231 mmcblk0p24 [COLOR="red"]<<< userdata partition has about 5.7 GB size[/COLOR]
179 32 30703616 mmcblk1
179 33 30703582 mmcblk1p1 [COLOR="red"]<<< this is your external sdcard partition[/COLOR]
get partition format
Code:
blkid
output:
Code:
/dev/block/mmcblk0p1: SEC_TYPE="msdos" UUID="00BC-614E" TYPE="vfat"
/dev/block/mmcblk0p10: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p19: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p20: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p21: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p22: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p23: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p24: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4" [COLOR="Red"]<<< userdata has ext4 format[/COLOR]
/dev/block/mmcblk1p1: UUID="02A3-21FE" LABEL="Volume" TYPE="exfat" [COLOR="Red"]<<< external sdcard has exfat format[/COLOR]
get currently mounted partitions
Code:
mount
output:
Code:
rootfs on / type rootfs (rw,seclabel)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,seclabel,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
none on /sys/fs/cgroup type tmpfs (rw,seclabel,relatime,mode=750,gid=1000)
none on /sys/fs/cgroup/memory type cgroup (rw,relatime,memory)
tmpfs on /mnt type tmpfs (rw,seclabel,relatime,mode=755,gid=1000)
none on /dev/memcg type cgroup (rw,relatime,memory)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
none on /sys/fs/cgroup/bfqio type cgroup (rw,relatime,bfqio)
/dev/block/mmcblk0p21 on /system type ext4 (ro,seclabel,relatime,data=ordered)
neither data nor external sdcard is mounted
mount your external sdcard
Code:
mkdir /mnt/sdext
mount /dev/block/mmcblk1p1 /mnt/sdext
extract your data partition as image to your sdcard
Code:
dd if=/dev/block/mmcblk0p24 of=/mnt/sdext/userdata.img
important info: as your data partition is larger than 4GB, you can only put the whole image to your sdcard if it is in exFat or NTFS format (fat32 does not allow files larger than 4GB). You could copy the image splitted like follows:
Code:
dd if=/dev/block/mmcblk0p24 of=/mnt/sdext/userdata_1.img count=4000000
dd if=/dev/block/mmcblk0p24 of=/mnt/sdext/userdata_2.img skip=4000000
copy your images later to pc and put it together in windows cmd with
Code:
copy /B userdata_1.img + userdata_2.img userdata.img
Not tested though.
look if there is enough space on your external sdcard
Code:
df -H
H=human readable sizes with 1000 based system; use no option to list number of 1k blocks; use -P do list 512byte blocks, usefull as dd uses same block size per default
output:
Code:
Filesystem Size Used Avail Use% Mounted on
tmpfs 708M 41k 708M 1% /dev
none 708M 0 708M 0% /sys/fs/cgroup
tmpfs 708M 0 708M 0% /mnt
/dev/block/mmcblk0p21 1.5G 986M 562M 64% /system
/dev/block/mmcblk0p24 [COLOR="red"]5.7G[/COLOR] 5.3G 423M 93% /mnt/userdata
/dev/block/mmcblk1p1 31G 14G [COLOR="red"]18G[/COLOR] 44% /mnt/sdext
or mount your internal data partition as well and copy only the data you need
Code:
mkdir /mnt/userdata
mount /dev/block/mmcblk0p24 /mnt/userdata
use cd and ls -al commands to find your desired data;
in a secondary cmd at your pc copy directly to your pc via e.g. (contacts, sms, photos, TWRP backup, ...)
Code:
adb pull /mnt/userdata/data/com.android.providers.contacts/databases/contacts2.db
adb pull /mnt/userdata/data/com.android.providers.telephony/databases/mmssms.db
adb pull /mnt/userdata/media/0/DCIM
adb pull /mnt/userdata/media/0/TWRP
However, copying whole directories often failed and resulted in reboot of phone...
So, what to do with this image?
Mounting it in windows as new drive worked very well with OSFMount. As windows can not read ext4 partitions, you might want to install a ext4 driver like ext2fsd. And there is your data. Interesting folders are /media/0 where your internal sdcard data (like photos) resides and /data where all your apps store its data. You can find your contacts here /data/com.android.providers.contacts/databases/contacts2.db and your SMS here /data/com.android.providers.telephony/databases/mmssms.db. You can copy this databases to your new phone or inspect them via sqlite3.exe from your Android Development Tools. Here is a macro that could convert your contacts to vcard.
Credits:
Many of these information can be found at various xda threads, i do not remember all threads where I got which information from. Everything here was written from mind. Google and Wikipedia is also helpfull when it comes to command details. However this thread contains also most of the commands i showed above. This thread might give some inspirations about reading ext4 partition images under windows. If you feel that another thread has to be mentioned here, please write a message and I'll add it.
Thank you for this clarify guide. I try it even if my phone isn't bricked.
GT-I9190 cihazımdan Tapatalk kullanılarak gönderildi
Edit. I managed to fix this and got it to work. The main problem was that my first window command had returned back with a prompt before I had time to complete the second window command. When I had the second window ready to hit return, I executed the first window command then imediately the second window command. It worked smoothly then extracting GB of data!
I have followed these instructions I found and they seem to work except the raw file resulting from them is 0 bytes. Any ideas?
I determined that my block for userdata is mmcblk0p21. All the commands in Cygwin return ok without problems. When in the second Cygwyn window and I do the nc 127.0.0.1 5555 | pv -i 0.5 > mmcblk0p21.raw the line returns no output back to the window other than the $ prompt.
I will paste the screen out put below these instructions I have followed.
The model is a Tab S SM-T800
1. Turn on your phone
2. Connect the phone in ADB mode
3. Unlock the screen.
4. Open a Cygwin terminal and enter (This assumes your BusyBox installation is at [/su/bin/busybox]. It may be at [/su/xbin/busybox]):
adb forward tcp:5555 tcp:5555
adb shell
su
/su/bin/busybox nc -l -p 5555 -e /su/bin/busybox dd if=/dev/block/mmcblk0p21
5. Open another Cygwin terminal and enter:
adb forward tcp:5555 tcp:5555
cd /nexus
nc 127.0.0.1 5555 | pv -i 0.5 > mmcblk0p21.raw
Screen output for the first window is.
[email protected] ~
$ adb forward tcp:5555 tcp:5555
[email protected] ~
$ adb shell
[email protected]:/ $ su
xbin/busybox nc -l -p 5555 -e /su/xbin/busybox dd if=/dev/block/mmcblk0p21 <
141|[email protected]:/ #
Screen output for the second window is.
[email protected] ~
$ adb forward tcp:5555 tcp:5555
[email protected] ~
$ cd /samsung
[email protected] /samsung
$ nc 127.0.0.1 5555 | pv -i 0.5 > mmcblk0p21.raw
[email protected] /samsung
$
I'm scrathcing my head as It is not finding any data.
I got the mmcblk0p21 from the following.
[email protected] ~
$ adb forward tcp:5555 tcp:5555
[email protected] ~
$ adb shell
[email protected]:/ $ mount
rootfs / rootfs ro,seclabel,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=1420076k,nr_inodes=114328,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
/sys/kernel/debug /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=1420076k,nr_inodes=114328,mode=750,gid=1000 0 0
tmpfs /mnt tmpfs rw,seclabel,relatime,size=1420076k,nr_inodes=114328,mode=755,gid=1000 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,size=1420076k,nr_inodes=114328,mode=700 0 0
tmpfs /mnt/secure/asec tmpfs rw,seclabel,relatime,size=1420076k,nr_inodes=114328,mode=700 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/dw_mmc.0/by-name/SYSTEM /system ext4 ro,seclabel,noatime,data=ordered 0 0
/dev/block/platform/dw_mmc.0/by-name/EFS /efs ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/dw_mmc.0/by-name/CACHE /cache ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/dw_mmc.0/by-name/USERDATA /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/dw_mmc.0/by-name/PERSDATA /persdata/absolute ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
tmpfs /storage tmpfs rw,seclabel,relatime,size=1420076k,nr_inodes=114328,mode=755,gid=1000 0 0
/dev/block/loop0 /su ext4 rw,seclabel,noatime,data=ordered 0 0
/data/knox/tmp_sdcard /mnt/knox sdcardfs rw,seclabel,nosuid,nodev,relatime,mask=0077 0 0
/data/knox/sdcard /mnt/knox/default/knox-emulated sdcardfs rw,seclabel,nosuid,nodev,relatime,low_uid=1000,low_gid=1000,gid=1015,multi_user,mask=0006 0 0
/data/knox/sdcard /mnt/knox/read/knox-emulated sdcardfs rw,seclabel,nosuid,nodev,relatime,low_uid=1000,low_gid=1000,gid=9997,multi_user,mask=0027 0 0
/data/knox/sdcard /mnt/knox/write/knox-emulated sdcardfs rw,seclabel,nosuid,nodev,relatime,low_uid=1000,low_gid=1000,gid=9997,multi_user,mask=0007 0 0
/data/media /mnt/runtime/default/emulated sdcardfs rw,seclabel,nosuid,nodev,noexec,relatime,low_uid=1023,low_gid=1023,gid=1015,multi_user,mask=0006,reserved=20MB 0 0
/data/media /storage/emulated sdcardfs rw,seclabel,nosuid,nodev,noexec,relatime,low_uid=1023,low_gid=1023,gid=1015,multi_user,mask=0006,reserved=20MB 0 0
/data/media /mnt/runtime/read/emulated sdcardfs rw,seclabel,nosuid,nodev,noexec,relatime,low_uid=1023,low_gid=1023,gid=9997,multi_user,mask=0027,reserved=20MB 0 0
/data/media /mnt/runtime/write/emulated sdcardfs rw,seclabel,nosuid,nodev,noexec,relatime,low_uid=1023,low_gid=1023,gid=9997,multi_user,mask=0007,reserved=20MB 0 0
1|[email protected]:/ $ ls -al /dev/block/platform/dw_mmc.0/by-name
lrwxrwxrwx root root 2017-01-28 09:13 BOOT -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2017-01-28 09:13 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2017-01-28 09:13 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2017-01-28 09:13 CACHE -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2017-01-28 09:13 CARRIER -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2017-01-28 09:13 CDMA-RADIO -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2017-01-28 09:13 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2017-01-28 09:13 HIDDEN -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2017-01-28 09:13 OTA -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2017-01-28 09:13 PARAM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2017-01-28 09:13 PERSDATA -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2017-01-28 09:13 RADIO -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2017-01-28 09:13 RECOVERY -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2017-01-28 09:13 RESERVED2 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2017-01-28 09:13 SYSTEM -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2017-01-28 09:13 TDATA -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2017-01-28 09:13 TOMBSTONES -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2017-01-28 09:13 USERDATA -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2017-01-28 09:13 m9kefs1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2017-01-28 09:13 m9kefs2 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2017-01-28 09:13 m9kefs3 -> /dev/block/mmcblk0p6
[email protected]:/ $
Hi,
As it said in another topics, do backup of your phone.
A scan of my config :
Code:
m8:/ # ls -al /dev/block/platform/msm_sdcc.1/by-name/
adsp -> /dev/block/mmcblk0p16
board_info -> /dev/block/mmcblk0p3
boot -> /dev/block/mmcblk0p42
cache -> /dev/block/mmcblk0p46
carrier -> /dev/block/mmcblk0p37
cdma_record -> /dev/block/mmcblk0p33
cir_img -> /dev/block/mmcblk0p40
control -> /dev/block/mmcblk0p30
custdata -> /dev/block/mmcblk0p22
ddr -> /dev/block/mmcblk0p14
debug_config -> /dev/block/mmcblk0p28
devlog -> /dev/block/mmcblk0p39
dsps -> /dev/block/mmcblk0p15
extra -> /dev/block/mmcblk0p32
fataldevlog -> /dev/block/mmcblk0p27
fsc -> /dev/block/mmcblk0p34
fsg -> /dev/block/mmcblk0p19
hboot -> /dev/block/mmcblk0p11
local -> /dev/block/mmcblk0p31
mfg -> /dev/block/mmcblk0p5
misc -> /dev/block/mmcblk0p24
modem_st1 -> /dev/block/mmcblk0p25
modem_st2 -> /dev/block/mmcblk0p26
pdata -> /dev/block/mmcblk0p29
pg1fs -> /dev/block/mmcblk0p2
pg2fs -> /dev/block/mmcblk0p6
radio -> /dev/block/mmcblk0p20
radio_config -> /dev/block/mmcblk0p18
recovery -> /dev/block/mmcblk0p43
reserve -> /dev/block/mmcblk0p41
reserve_1 -> /dev/block/mmcblk0p4
reserve_2 -> /dev/block/mmcblk0p23
reserve_3 -> /dev/block/mmcblk0p44
rpm -> /dev/block/mmcblk0p8
sbl1 -> /dev/block/mmcblk0p1
sbl1_update -> /dev/block/mmcblk0p7
sdi -> /dev/block/mmcblk0p10
sensor_hub -> /dev/block/mmcblk0p38
skylink -> /dev/block/mmcblk0p36
sp1 -> /dev/block/mmcblk0p12
ssd -> /dev/block/mmcblk0p35
system -> /dev/block/mmcblk0p45
tool_diag -> /dev/block/mmcblk0p21
tz -> /dev/block/mmcblk0p9
userdata -> /dev/block/mmcblk0p47
wcnss -> /dev/block/mmcblk0p17
wifi -> /dev/block/mmcblk0p13
So i have already do a backup of all partition (to .bin files) but as it said in the folliwing topic,
https://forum.xda-developers.com/showthread.php?t=2450045
If the partition is formatted as ext3/4 then the dumped partition will have .img as an extension.
Other partition dumps have different extensions; examples:
radio.bin
param.lfs
Sbl.bin
zImage (without extension)
Click to expand...
Click to collapse
What's possible to launch for zImage (without extension)? The following command ?
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/mfg of=mfg.zImage
or just .img extension file is okey for reflashing ?
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/mfg of=mfg.zImage
A script already exist to backup all partition ? an example : https://forum.xda-developers.com/showthread.php?t=2073775
--------------------------------------------------------------------------------------------------------
Moroever, can we create .tar.md5 for flashing BL, AP, CSC, ?
The following old code, we can create .tar.md5 files with X part.
A template exist for htc one m8?
https://forum.xda-developers.com/showthread.php?t=2417603%3Cbr%20/%3E[Backup%20Script]Backup%20all%20paritions%20on%20i9505%20to%20odin%20rom
Code:
echo "Making compressed tar ball"
busybox tar -cz NON-HLOS.bin modem.bin sbl1.mbn sbl2.mbn sbl3.mbn aboot.mbn rpm.mbn tz.mbn system.img.ext4 recovery.img boot.img cache.img.ext4 > odin-${GETDATE}.tar.gz
echo "Writing MD5 sums..."
busybox md5sum -t odin-${GETDATE}.tar.gz >> odin-${GETDATE}.tar.gz
echo "Renaming..."
busybox mv odin-${GETDATE}.tar.gz odin-${GETDATE}.tar.md5.gz