Develop Bugs

[Q] Backup/Restore using DD and ODIN

Any help will be appreciated :good:​
As you know backup and restore partitions can be done using dd command in linux.
I know it's not noob friendly, but since custom kernels and recoveries raises flash counter, it's a good idea.
rotohammer has made a detailed explanation here for Galaxy Tab.
So all we need the block device list for note 2
/dev/block/mmcblk0 Whole Internal Storage
/dev/block/mmcblk0p1 4194kB BOTA0
/dev/block/mmcblk0p2 4194kB BOTA1
/dev/block/mmcblk0p3 21.0MB EFS
/dev/block/mmcblk0p4 4194kB m9kefs1
/dev/block/mmcblk0p5 4194kB m9kefs2
/dev/block/mmcblk0p6 4194kB m9kefs3
/dev/block/mmcblk0p7 8389kB PARAM
/dev/block/mmcblk0p8 8389kB BOOT (Kernel)
/dev/block/mmcblk0p9 8389kB RECOVERY
/dev/block/mmcblk0p10 92.3MB RADIO (Modem)
/dev/block/mmcblk0p11 4194kB TOMBSTONES
/dev/block/mmcblk0p12 1434MB CACHE
/dev/block/mmcblk0p13 2147MB SYSTEM
/dev/block/mmcblk0p14 587MB HIDDEN
/dev/block/mmcblk0p15 8389kB OTA
/dev/block/mmcblk0p16 11.4GB USERDATA (User Accessible Storage and /DATA folder)

[email protected] said:
As you know backup and restore partitions can be done using dd command in linux.
I know it's not noob friendly, but since custom kernels and recoveries raises flash counter, it's a good idea.
rotohammer has made a detailed explanation here for Galaxy Tab.
So I need all the block device list for note 2
So far I know
/dev/block/mmcblk0p13 = /system
/dev/block/mmcblk0p12 = /cache
/dev/block/mmcblk0p16 = /data
/dev/block/mmcblk0p3 = /efs
/dev/block/mmcblk0p9 = /recovery
/dev/block/mmcblk0p8 = /boot (kernel)
I'm not a linux expert, can somebody confirm/correct these?
Click to expand...
Click to collapse
Perhaps you should find out what the mount command does before you start using dd to read and write directly to the partitions. These sort of commands don't take prisoners

I said I'm not a linux expert, it doesn't mean I'm totally noob. I'm using Lubuntu on my netbook.
I'm well aware of risks, I'm using dd on PC time to time.
Mount only shows mounted partitions. I'm asking those partitions. I couldn't find a full partitions list anywhere
There are many partitions and I want to know what they are
Code:
cat /proc/partitions
major minor #blocks name
179 0 15388672 mmcblk0
179 1 4096 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 4096 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 8192 mmcblk0p7
179 8 8192 mmcblk0p8
179 9 8192 mmcblk0p9
179 10 90112 mmcblk0p10
179 11 4096 mmcblk0p11
179 12 1400832 mmcblk0p12
179 13 2097152 mmcblk0p13
179 14 573440 mmcblk0p14
179 15 8192 mmcblk0p15
259 0 11141120 mmcblk0p16
179 16 62367744 mmcblk1
179 17 62351360 mmcblk1p1
[email protected]:/ # ls -l /dev/block/mmcblk*
ls -l /dev/block/mmcblk*
brw------- root root 179, 0 2013-04-01 00:14 mmcblk0
brw------- root root 179, 1 2013-04-01 00:14 mmcblk0p1
brw-rw---- system radio 179, 10 2013-04-01 00:14 mmcblk0p10
brw-rw---- system radio 179, 11 2013-04-01 00:14 mmcblk0p11
brw------- root root 179, 12 2013-04-01 00:14 mmcblk0p12
brw------- root root 179, 13 2013-04-01 00:14 mmcblk0p13
brw------- root root 179, 14 2013-04-01 00:14 mmcblk0p14
brw------- root root 179, 15 2013-04-01 00:14 mmcblk0p15
brw------- root root 259, 0 2013-04-01 00:14 mmcblk0p16
brw------- root root 179, 2 2013-04-01 00:14 mmcblk0p2
brw------- root root 179, 3 2013-04-01 00:14 mmcblk0p3
brw-rw---- system radio 179, 4 2013-04-01 00:14 mmcblk0p4
brw-rw---- system radio 179, 5 2013-04-01 00:14 mmcblk0p5
brw-rw---- system radio 179, 6 2013-04-01 00:14 mmcblk0p6
brw-rw---- system root 179, 7 2013-04-01 00:14 mmcblk0p7
brw------- root root 179, 8 2013-04-01 00:14 mmcblk0p8
brw------- root root 179, 9 2013-04-01 00:14 mmcblk0p9
brw------- root root 179, 16 2013-04-01 00:14 mmcblk1
brw------- root root 179, 17 2013-04-01 00:14 mmcblk1p1
For some reason listing partitions by-label doesn't work either for android or block devices.
Code:
[email protected]:/ # ls -l /dev/block/by-label
ls -l /dev/block/by-label
/dev/block/by-label: No such file or directory

[email protected] said:
...So far I know
/dev/block/mmcblk0p13 = /system
/dev/block/mmcblk0p12 = /cache
/dev/block/mmcblk0p16 = /data
/dev/block/mmcblk0p3 = /efs
/dev/block/mmcblk0p9 = /recovery
/dev/block/mmcblk0p8 = /boot (kernel)
I'm not a linux expert, can somebody confirm/correct these?
Click to expand...
Click to collapse
These partitions are correct. Radio/modem partition is missing. /dev/block/mmcblk0p10 = /modem/baseband/radio
Edit:
For the list of all partitions, use 'parted' command.
Partitions from the international GNote2 N7100 are:
Code:
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. Alle Rechte vorbehalten.
C:\Users\cargo>cd tools
C:\Users\cargo\tools>adb shell
~ # ←[6nparted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: MMC VTU00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 8389kB 4194kB BOTA0
2 8389kB 12.6MB 4194kB BOTA1
3 12.6MB 33.6MB 21.0MB ext4 EFS
4 33.6MB 37.7MB 4194kB m9kefs1
5 37.7MB 41.9MB 4194kB m9kefs2
6 41.9MB 46.1MB 4194kB m9kefs3
7 46.1MB 54.5MB 8389kB PARAM
8 54.5MB 62.9MB 8389kB BOOT
9 62.9MB 71.3MB 8389kB RECOVERY
10 71.3MB 164MB 92.3MB RADIO
11 164MB 168MB 4194kB TOMBSTONES
12 168MB 1602MB 1434MB ext4 CACHE
13 1602MB 3750MB 2147MB ext4 SYSTEM
14 3750MB 4337MB 587MB ext4 HIDDEN
15 4337MB 4345MB 8389kB OTA
16 4345MB 15.8GB 11.4GB ext4 USERDATA
(parted)

cargobr151 said:
These partitions are correct. Radio/modem partition is missing. /dev/block/mmcblk0p10 = /modem/baseband/radio
Edit:
For the list of all partitions, use 'parted' command.
Partitions from the international GNote2 N7100 are:
Code:
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. Alle Rechte vorbehalten.
C:\Users\cargo>cd tools
C:\Users\cargo\tools>adb shell
~ # ←[6nparted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: MMC VTU00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 8389kB 4194kB BOTA0
2 8389kB 12.6MB 4194kB BOTA1
3 12.6MB 33.6MB 21.0MB ext4 EFS
4 33.6MB 37.7MB 4194kB m9kefs1
5 37.7MB 41.9MB 4194kB m9kefs2
6 41.9MB 46.1MB 4194kB m9kefs3
7 46.1MB 54.5MB 8389kB PARAM
8 54.5MB 62.9MB 8389kB BOOT
9 62.9MB 71.3MB 8389kB RECOVERY
10 71.3MB 164MB 92.3MB RADIO
11 164MB 168MB 4194kB TOMBSTONES
12 168MB 1602MB 1434MB ext4 CACHE
13 1602MB 3750MB 2147MB ext4 SYSTEM
14 3750MB 4337MB 587MB ext4 HIDDEN
15 4337MB 4345MB 8389kB OTA
16 4345MB 15.8GB 11.4GB ext4 USERDATA
(parted)
Click to expand...
Click to collapse
Thank you a lot, parted is not working on mine. Probably busybox related?
Edit: Nevermind I found the executable file of parted . Worked fine. Thanks again.

You must have installed a custom recovery. (with parted command included)
Like cwm or twrp v2.4.4.0. I use twrp v2.4.4.0.

@OP updated my thread with this thread info...You can visit here

@[email protected]
So continue here
Question is if we makes tar file form dump file we have created like system.img, can we flash it with odin?

dr.ketan said:
@[email protected]
So continue here
Question is if we makes tar file form dump file we have created like system.img, can we flash it with odin?
Click to expand...
Click to collapse
Roger that
here http://forum.xda-developers.com/showthread.php?t=1777579 @das7982 well explained the instructions for Galaxy SIII
According to his post, he's recommending to make an ODIN package from only system.img
To make system.img of note 2
Code:
dd if=/dev/block/mmcblk0p13 of=/storage/extSdCard/system.img bs=4096
Here we need a linux pc or Cygwin for Windows. If we going to use Cygwin, we need to install it along with tar, md5sum commands
Code:
tar -H ustar -c system.img > system.img.tar
Then we need to make Md5 checksum
Code:
md5sum -t system.img.tar >> system.img.tar
rename it
Code:
mv system.img.tar system.img.tar.md5
I haven't tried this yet but I'll try soon

I have already made this and also in try to test it.
Sent from my GT-N7100 using xda premium
---------- Post added at 11:00 PM ---------- Previous post was at 10:55 PM ----------
I have read it, I think it shouldn't raise counter unless we have custom recovery /kernel
B'coz I don't think custom tar will raise counter, i am regularly extract recovery and kernel from stock and packing it separately in tar, it never raised counter.
Sent from my GT-N7100 using xda premium

dr.ketan said:
I have already made this and also in try to test it.
Sent from my GT-N7100 using xda premium
---------- Post added at 11:00 PM ---------- Previous post was at 10:55 PM ----------
I have read it, I think it shouldn't raise counter unless we have custom recovery /kernel
B'coz I don't think custom tar will raise counter, i am regularly extract recovery and kernel from stock and packing it separately in tar, it never raised counter.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
You're correct, stock kernel and recovery shouldn't increase the flash counter.
To backup /data we can use
Code:
adb shell
stop
busybox tar -cZvf /storage/extSdCard/data.ext4.tar --exclude media --exclude dalvik-cache /data
reboot
To restore
Code:
adb shell
stop
busybox tar -xvf /storage/extSdCard/data.ext4.tar -C /
reboot

[Q] FXP319 soft bricked my c1905?

Hi,
recently i updated via CWM my unblocked, rooted xperia m (C1905). Phone has FXP317, earlier i updated radio installing stock 4.3 and it going well, besides fatal GPS, as usual
After upgrade form FXP317 to FXP319 and reboot phone, it running veeeryy slow and suddenly hangs up. After restart to CWM (it lasts couple minutes), i try to install it again (install from zip) and it failed - it shows problem with mounting /DATA.
Now i attempt to format /DATA but it failed - CWM says that partition can't be mounted.
Another try - flash stock rom (Flasher form Androxyde) gives
Code:
19/048/2014 07:48:57 - INFO - Device connected in flash mode
19/049/2014 07:49:06 - INFO - Selected Bundle for Xperia M C1905. FW release : Google Android 4.3 (Jelly Bean). Customization : 15.4.A.0.23
19/049/2014 07:49:06 - INFO - Preparing files for flashing
19/049/2014 07:49:53 - INFO - Please connect your device into flashmode.
19/049/2014 07:49:54 - INFO - Opening device for R/W
19/049/2014 07:49:54 - INFO - Reading device information
19/049/2014 07:49:54 - INFO - Phone ready for flashmode operations.
19/049/2014 07:49:54 - INFO - Current device : Unknown: Mar 7 2014/10:51:59 - YT910M7GB9 - Unknown: Mar 7 2014/10:51:59 - Unknown: Mar 7 2014/10:51:59 - Unknown: Mar 7 2014/10:51:59
19/049/2014 07:49:54 - INFO - Start Flashing
19/049/2014 07:49:54 - INFO - Processing loader.sin
19/049/2014 07:49:54 - INFO - Checking header
19/049/2014 07:49:54 - INFO - Flashing data
19/049/2014 07:49:55 - INFO - Processing of loader.sin finished.
19/049/2014 07:49:55 - INFO - Loader : S1_Root_dbe9 - Version : loader_MSM8X30_10 / Boot version : S1_Boot_MSM_8227_5 / Bootloader status : ROOTED
19/049/2014 07:49:55 - INFO - Processing partition-image.sin
19/049/2014 07:49:55 - INFO - Checking header
19/049/2014 07:49:55 - INFO - Flashing data
19/049/2014 07:49:55 - INFO - Processing of partition-image.sin finished.
19/049/2014 07:49:55 - INFO - Parsing boot delivery
19/049/2014 07:49:55 - INFO - Phone boot version : S1_Boot_MSM_8227_5. Boot delivery version : S1_Boot_MSM_8227_5
19/049/2014 07:49:55 - INFO - Boot delivery up to date. Nothing to do
19/049/2014 07:49:55 - INFO - Processing kernel.sin
19/049/2014 07:49:55 - INFO - Checking header
19/049/2014 07:49:55 - INFO - Flashing data
19/049/2014 07:49:55 - ERROR - Processing of kernel.sin finished with errors.
19/049/2014 07:49:55 - INFO - Ending flash session
19/049/2014 07:49:55 - ERROR - ERR_SEVERITY="MINOR";ERR_CODE="0017";ERR_DYNAMIC="0x8020001C ";
Soft from SONY - SUS, PC Companion, EMMA did't recognize my phone and gives up.
Meanwhile i flash kernel and i made fatal mistake (i thought so) - i tried to flash wrong kernel (it has 83 bytes), but after choosing the right file I could install the appropriate kernel.
Now i have CWM 6.0.4.8, and i can connect phone in flash mode, also in fastboot but i can't flash any rom because i can't mount /data
Command adb devices -l gives
List of devices attached
YT910M7GB9 recovery product:C1905 model:C1905 device:nicki
How to mount /data or how to do the re-partition? What should I do to flash the stock rom?

Have you flashed the stock ROM again? Does it still show the same error?

elmkzgirxp said:
Have you flashed the stock ROM again? Does it still show the same error?
Click to expand...
Click to collapse
Yes, i did and same again. I have stock ROM 4.1.2, stock ROM 4.3. One thing - phone starts and - after maybe 30 min or so - stops on "Encryption unsuccessful bla bla bla". I try even recovery backup form http://forum.xda-developers.com/showthread.php?p=51574842 but it failed - folder /system cannot be restored.
I'm thinking about partitioning internal memory, but i don't know how. I have an access via flashmode and i'm looking for solution about using adb

Encryption? How'd that get there?

elmkzgirxp said:
Encryption? How'd that get there?
Click to expand...
Click to collapse
In my case - remove battery, wait 5 sec, i turn on the phone and wait about 30 min - after that long boot this is all i see.

TomekParuszewski said:
In my case - remove battery, wait 5 sec, i turn on the phone and wait about 30 min - after that long boot this is all i see.
Click to expand...
Click to collapse
Why not refer here... This might solve your problem.

elmkzgirxp said:
Why not refer here... This might solve your problem.
Click to expand...
Click to collapse
Thx, so far i don't find exactly the same problem as mine, but now i try rubber band trick. I don't know how this will help, will see

Exact same problem
With fxp 18

TomekParuszewski said:
Thx, so far i don't find exactly the same problem as mine, but now i try rubber band trick. I don't know how this will help, will see
Click to expand...
Click to collapse
Hmm, according to the definition of soft brick, and therefore that I can enter fastboot mode and flashmode and CWM, the phone is not soft bricked, but there is a problem with partitions or privileges SU, because I can not reflash rom. The system is still not able to mount the directory / data.
I will try connect to phone by the adb command and see, err, i don't know what - i must check available commands. Right now i'm waiting for CWM

After get into adb shell i get:
Code:
C:\SDK\sdk\platform-tools>adb shell
~ # ←[6nsu
su
/sbin/sh: su: not found
~ # ←[6ndf
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 440892 128 440764 0% /dev
tmpfs 440892 8 440884 0% /tmp
tmpfs 440892 0 440892 0% /storage
tmpfs 440892 0 440892 0% /mnt/secure
tmpfs 440892 0 440892 0% /mnt/fuse
/dev/block/platform/msm_sdcc.1/by-name/cache
252136 4660 247476 2% /cache
~ # ←[6nls -l
ls -l
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
drwxr-xr-x 2 root root 0 May 21 04:33 boot
-rw-r--r-- 1 root root 579 May 21 04:33 boot.txt
drwxrwx--x 6 system cache 4096 May 17 10:36 cache
-rwxr-x--- 1 root root 284696 May 21 04:33 charger
drwxr-xr-x 3 root root 0 May 21 04:33 data
drwxr-xr-x 2 root root 0 May 21 04:33 datadata
-rw-r--r-- 1 root root 3920 May 21 04:33 default.prop
drwxr-xr-x 10 root root 3260 May 21 04:33 dev
drwxr-xr-x 2 root root 0 May 21 04:33 emmc
drwxr-xr-x 2 root root 0 May 21 04:33 etc
drwxr-xr-x 2 root root 0 May 21 04:33 external_sd
-rw-r--r-- 1 root root 10961 May 21 04:33 file_contexts
-rw-r----- 1 root root 1213 May 21 04:33 fstab.qcom
-rwxr-x--- 1 root root 187840 May 21 04:33 init
-rwxr-x--- 1 root root 2704 May 21 04:33 init.qcom.syspart_fixup.sh
-rwxr-x--- 1 root root 2892 May 21 04:33 init.rc
-rwxr-x--- 1 root root 512 May 21 04:33 init.recovery.qcom.rc
drwxr-xr-x 2 root root 0 May 21 04:33 internal_sd
-rw-r--r-- 1 root root 14452 Jan 1 1970 logo.rle
drwxrwxr-x 5 root system 0 May 21 04:33 mnt
dr-xr-xr-x 131 root root 0 Jan 1 1970 proc
-rw-r--r-- 1 root root 2161 May 21 04:33 property_contexts
drwxr-xr-x 2 root root 0 May 21 04:33 recovery
drwxr-xr-x 3 root root 0 May 21 04:33 res
drwx------ 2 root root 0 May 13 22:52 root
drwxr-x--- 2 root root 0 May 21 04:33 sbin
drwxr-xr-x 2 root root 0 May 21 04:33 sd-ext
lrwxrwxrwx 1 root root 11 May 21 04:33 sdcard -> /data/media
-rw-r--r-- 1 root root 660 May 21 04:33 seapp_contexts
-rw-r--r-- 1 root root 95689 May 21 04:33 sepolicy
d---r-x--- 2 root sdcard_r 40 May 21 04:33 storage
dr-xr-xr-x 14 root root 0 May 21 04:33 sys
drwxr-xr-x 3 root root 0 May 21 04:33 system
drwxrwxr-x 2 root shell 60 May 21 04:33 tmp
-rw-r--r-- 1 root root 8196 May 21 04:33 ueventd.qcom.rc
-rw-r--r-- 1 root root 7275 May 21 04:33 ueventd.rc
C:\SDK\sdk\platform-tools>adb remount
remount failed: Success
C:\SDK\sdk\platform-tools>adb devices -l
List of devices attached
YT910M7GB9 recovery product:C1905 model:C1905 device:nicki
C:\SDK\sdk\platform-tools>adb shell
~ # ←[6nls -l
ls -l
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
drwxr-xr-x 2 root root 0 May 21 04:33 boot
-rw-r--r-- 1 root root 579 May 21 04:33 boot.txt
drwxrwx--x 6 system cache 4096 May 17 10:36 cache
-rwxr-x--- 1 root root 284696 May 21 04:33 charger
drwxr-xr-x 3 root root 0 May 21 04:33 data
drwxr-xr-x 2 root root 0 May 21 04:33 datadata
-rw-r--r-- 1 root root 3920 May 21 04:33 default.prop
drwxr-xr-x 10 root root 3260 May 21 04:33 dev
drwxr-xr-x 2 root root 0 May 21 04:33 emmc
drwxr-xr-x 2 root root 0 May 21 04:33 etc
drwxr-xr-x 2 root root 0 May 21 04:33 external_sd
-rw-r--r-- 1 root root 10961 May 21 04:33 file_contexts
-rw-r----- 1 root root 1213 May 21 04:33 fstab.qcom
-rwxr-x--- 1 root root 187840 May 21 04:33 init
-rwxr-x--- 1 root root 2704 May 21 04:33 init.qcom.syspart_fixup.sh
-rwxr-x--- 1 root root 2892 May 21 04:33 init.rc
-rwxr-x--- 1 root root 512 May 21 04:33 init.recovery.qcom.rc
drwxr-xr-x 2 root root 0 May 21 04:33 internal_sd
-rw-r--r-- 1 root root 14452 Jan 1 1970 logo.rle
drwxrwxr-x 5 root system 0 May 21 04:33 mnt
dr-xr-xr-x 131 root root 0 Jan 1 1970 proc
-rw-r--r-- 1 root root 2161 May 21 04:33 property_contexts
drwxr-xr-x 2 root root 0 May 21 04:33 recovery
drwxr-xr-x 3 root root 0 May 21 04:33 res
drwx------ 2 root root 0 May 13 22:52 root
drwxr-x--- 2 root root 0 May 21 04:33 sbin
drwxr-xr-x 2 root root 0 May 21 04:33 sd-ext
lrwxrwxrwx 1 root root 11 May 21 04:33 sdcard -> /data/media
-rw-r--r-- 1 root root 660 May 21 04:33 seapp_contexts
-rw-r--r-- 1 root root 95689 May 21 04:33 sepolicy
d---r-x--- 2 root sdcard_r 40 May 21 04:33 storage
dr-xr-xr-x 14 root root 0 May 21 04:33 sys
drwxr-xr-x 3 root root 0 May 21 04:33 system
drwxrwxr-x 2 root shell 60 May 21 04:33 tmp
-rw-r--r-- 1 root root 8196 May 21 04:33 ueventd.qcom.rc
-rw-r--r-- 1 root root 7275 May 21 04:33 ueventd.rc
~ # ←[6ndf
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 440892 128 440764 0% /dev
tmpfs 440892 8 440884 0% /tmp
tmpfs 440892 0 440892 0% /storage
tmpfs 440892 0 440892 0% /mnt/secure
tmpfs 440892 0 440892 0% /mnt/fuse
/dev/block/platform/msm_sdcc.1/by-name/cache
252136 4660 247476 2% /cache
C:\SDK\sdk\platform-tools>adb shell
~ # ←[6ndf -h
df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 430.6M 128.0K 430.4M 0% /dev
tmpfs 430.6M 8.0K 430.6M 0% /tmp
tmpfs 430.6M 0 430.6M 0% /storage
tmpfs 430.6M 0 430.6M 0% /mnt/secure
tmpfs 430.6M 0 430.6M 0% /mnt/fuse
/dev/block/platform/msm_sdcc.1/by-name/cache
246.2M 4.6M 241.7M 2% /cache
~ # ←[6nfdisk
fdisk
BusyBox v1.22.1 static (2014-04-06 21:24 +0200) multi-call binary.
Usage: fdisk [-ul] [-C CYLINDERS] [-H HEADS] [-S SECTORS] [-b SSZ] DISK
Change partition table
-u Start and End are in sectors (instead of cylinders)
-l Show partition table for each DISK, then exit
-b 2048 (for certain MO disks) use 2048-byte sectors
-C CYLINDERS Set number of cylinders/heads/sectors
-H HEADS
-S SECTORS
~ # ←[6nfdisk -l
fdisk -l
~ # ←[6nfdisk -l
fdisk -l
~ # ←[6n^C
C:\SDK\sdk\platform-tools>
C:\SDK\sdk\platform-tools>adb shell
~ # ←[6nls
ls
boot logo.rle
boot.txt mnt
cache proc
charger property_contexts
data recovery
datadata res
default.prop root
dev sbin
emmc sd-ext
etc sdcard
external_sd seapp_contexts
file_contexts sepolicy
fstab.qcom storage
init sys
init.qcom.syspart_fixup.sh system
init.rc tmp
init.recovery.qcom.rc ueventd.qcom.rc
internal_sd ueventd.rc
~ # ←[6ndf
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 440892 128 440764 0% /dev
tmpfs 440892 8 440884 0% /tmp
tmpfs 440892 0 440892 0% /storage
tmpfs 440892 0 440892 0% /mnt/secure
tmpfs 440892 0 440892 0% /mnt/fuse
/dev/block/platform/msm_sdcc.1/by-name/cache
252136 4660 247476 2% /cache
~ # ←[6ncd data
cd data
/data # ←[6nls
ls
media
/data # ←[6n^C
C:\SDK\sdk\platform-tools>adb shell
~ # ←[6nls -l
ls -l
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
drwxr-xr-x 2 root root 0 May 21 04:33 boot
-rw-r--r-- 1 root root 579 May 21 04:33 boot.txt
drwxrwx--x 6 system cache 4096 May 17 10:36 cache
-rwxr-x--- 1 root root 284696 May 21 04:33 charger
drwxr-xr-x 3 root root 0 May 21 04:33 data
drwxr-xr-x 2 root root 0 May 21 04:33 datadata
-rw-r--r-- 1 root root 3920 May 21 04:33 default.prop
drwxr-xr-x 10 root root 3260 May 21 04:33 dev
drwxr-xr-x 2 root root 0 May 21 04:33 emmc
drwxr-xr-x 2 root root 0 May 21 04:33 etc
drwxr-xr-x 2 root root 0 May 21 04:33 external_sd
-rw-r--r-- 1 root root 10961 May 21 04:33 file_contexts
-rw-r----- 1 root root 1213 May 21 04:33 fstab.qcom
-rwxr-x--- 1 root root 187840 May 21 04:33 init
-rwxr-x--- 1 root root 2704 May 21 04:33 init.qcom.syspart_fixup.sh
-rwxr-x--- 1 root root 2892 May 21 04:33 init.rc
-rwxr-x--- 1 root root 512 May 21 04:33 init.recovery.qcom.rc
drwxr-xr-x 2 root root 0 May 21 04:33 internal_sd
-rw-r--r-- 1 root root 14452 Jan 1 1970 logo.rle
drwxrwxr-x 5 root system 0 May 21 04:33 mnt
dr-xr-xr-x 131 root root 0 Jan 1 1970 proc
-rw-r--r-- 1 root root 2161 May 21 04:33 property_contexts
drwxr-xr-x 2 root root 0 May 21 04:33 recovery
drwxr-xr-x 3 root root 0 May 21 04:33 res
drwx------ 2 root root 0 May 13 22:52 root
drwxr-x--- 2 root root 0 May 21 04:33 sbin
drwxr-xr-x 2 root root 0 May 21 04:33 sd-ext
lrwxrwxrwx 1 root root 11 May 21 04:33 sdcard -> /data/media
-rw-r--r-- 1 root root 660 May 21 04:33 seapp_contexts
-rw-r--r-- 1 root root 95689 May 21 04:33 sepolicy
d---r-x--- 2 root sdcard_r 40 May 21 04:33 storage
dr-xr-xr-x 14 root root 0 May 21 04:33 sys
drwxr-xr-x 3 root root 0 May 21 04:33 system
drwxrwxr-x 2 root shell 60 May 21 04:33 tmp
-rw-r--r-- 1 root root 8196 May 21 04:33 ueventd.qcom.rc
-rw-r--r-- 1 root root 7275 May 21 04:33 ueventd.rc
I don't have any information about partitions (filesystem tmpfs)!

TomekParuszewski said:
I don't have any information about partitions (filesystem tmpfs)!
Click to expand...
Click to collapse
Firstly you need mount partitions through recovery: item mounts and storage
Also from there try to format all of them and then flash via flashtool / via ZIP / restore backup.
Here is possibility that your NAND-flash (internal 4GB memory chip) broken or have a lot bad sectors.

Bonoboo said:
Firstly you need mount partitions through recovery: item mounts and storage
Also from there try to format all of them and then flash via flashtool / via ZIP / restore backup.
Here is possibility that your NAND-flash (internal 4GB memory chip) broken or have a lot bad sectors.
Click to expand...
Click to collapse
Unfortunately, I can not mount / data or / system. After a very long time the command mount / data, then throws an error, the contents of which I can not remember now. I will try to rewrite its contents exactly as it appears. is below:
(i'm wainting rught now - 14:29)
I have version 6.0.4.8 CWM and I see no formatting options. I tried to upload the CWM 6.0.4.7 from this post http://forum.xda-developers.com/showthread.php?t=2494793 but I could not do that. I still have my version. My bad, of course i have format command.
Does this mean that my phone died? Do I still have any chance to fix it?

TomekParuszewski said:
After a very long time the command mount / data, then throws an error, the contents of which I can not remember now. I will try to rewrite its contents exactly as it appears.
Click to expand...
Click to collapse
Command from ADB? Try from recovery menu.
And output of command will be helpful.
TomekParuszewski said:
Does this mean that my phone died?
Click to expand...
Click to collapse
Don't give up for now.
UPD: I googled ERR_DYNAMIC=0x8020001C and found 7 threads with same problem with Xperia M:
1, 2, 3, 4, 5, 6, 7
All them have error while flashing different parts: kernel and data.
And no solution there for now.

Bonoboo said:
Command from ADB? Try from recovery menu.
And output of command will be helpful.
Don't give up for now.
Click to expand...
Click to collapse
thank you for your words of encouragement - I'm gonna fight to the end
BTW - in time when i'm waiting to output for command mount /data from recovery, I have access to the phone via adb (but it's normal after all, i suppose)

Bonoboo said:
UPD: I googled ERR_DYNAMIC=0x8020001C and found 6 threads with same problem with Xperia M:
1, 2, 3, 4, 5, 6
All them have error while flashing different parts: kernel and data.
And no solution there for now.
Click to expand...
Click to collapse
yes, most of them i've seen, thx

Just info :
Re-partition method not available for now.
Maybe when flashing via flashtool keep tick only on partition-image.sin restore stock.
There is some method to erase internal memory via adb, but it for other model.
And I don't know will it help here.
Questions:
1. So your device not was encrypted, right?
2. Try mounts and storage > format all
3. Try mount via menu in recovery

Bonoboo said:
Just info :
Re-partition method not available for now.
Maybe when flashing via flashtool keep tick only on partition-image.sin restore stock.
There is some method to erase internal memory via adb, but it for other model.
And I don't know will it help here.
Questions:
1. So your device not was encrypted, right?
3. You sure that in mounts and storage no format options?
4. Try mount via menu in recovery?
2. How about post error while mounting?
Click to expand...
Click to collapse
Answers:
If i'm wait long enough, phone boot to screen "Encryption unsuccessful", so i don't know - I do not encrypt the phone as I remember
Sorry, of course there is format command in recovery, my bad
I will try again and write exact message from the screen

Sorry for messing numbers, I edited post.
TomekParuszewski said:
in time when i'm waiting to output for command mount /data from recovery, I have access to the phone via adb (but it's normal after all, i suppose)
Click to expand...
Click to collapse
Seems not. Reboot.
Try formatting.
Just note about adb output earlier.
ls shows temporary FS that recovery creates in RAM.
By fact blocks devices in /dev/block/ and we can do something with them, like recreate partitions using mke2fs
Or erase them by dd if=/dev/zero
Try commands:
cat /proc/partitions
mount
fdisk -l /dev/block/mmcblk0p17
fdisk -l /dev/block/mmcblk0p5
And try flashing via flashtool:
– untick wipe data and cache
– tick all in Exclude section except partition
Here useful commands (similar problem for Samsung, restoring partition table helps)
And here list of all our partitions relatively number:
FOTAKernel -> /dev/block/mmcblk0p23
LTALabel -> /dev/block/mmcblk0p16
TA -> /dev/block/mmcblk0p1
aboot -> /dev/block/mmcblk0p6
alt_aboot -> /dev/block/mmcblk0p12
alt_rpm -> /dev/block/mmcblk0p15
alt_s1sbl2 -> /dev/block/mmcblk0p10
alt_sbl1 -> /dev/block/mmcblk0p8
alt_sbl2 -> /dev/block/mmcblk0p9
alt_sbl3 -> /dev/block/mmcblk0p11
alt_tz -> /dev/block/mmcblk0p13
boot -> /dev/block/mmcblk0p17
cache -> /dev/block/mmcblk0p26
fsg -> /dev/block/mmcblk0p21
modem -> /dev/block/mmcblk0p18
modemst1 -> /dev/block/mmcblk0p19
modemst2 -> /dev/block/mmcblk0p20
persist -> /dev/block/mmcblk0p24
ramdump -> /dev/block/mmcblk0p22
rpm -> /dev/block/mmcblk0p14
s1sbl2 -> /dev/block/mmcblk0p4
sbl1 -> /dev/block/mmcblk0p2
sbl2 -> /dev/block/mmcblk0p3
sbl3 -> /dev/block/mmcblk0p5
system -> /dev/block/mmcblk0p25
tz -> /dev/block/mmcblk0p7
userdata -> /dev/block/mmcblk0p27

Bonoboo said:
Sorry for messing numbers, I edited post.
Seems not. Reboot.
Try formatting.
Just note about adb output earlier.
ls shows temporary FS that recovery creates in RAM.
By fact blocks devices in /dev/block/ and we can do something with them, like recreate partitions using mke2fs
Or erase them by dd if=/dev/zero
Try commands:
cat /proc/partitions
mount
fdisk -l /dev/block/mmcblk0p17
fdisk -l /dev/block/mmcblk0p5
And try flashing via flashtool:
– untick wipe data and cache
– tick all in Exclude section except partition
Here useful commands (similar problem for Samsung, restoring partition table helps)
And here list of all our partitions relatively number:
Click to expand...
Click to collapse
ok, here the log from CWM - i don't know when each event occurred
Code:
persist.audio.low.latency.rec=false
persist.debug.wfd.enable=1
persist.radio.apm_sim_not_pwdn=1
persist.timed.enable=true
persist.fuse_sdcard=true
keyguard.no_require_sim=true
telephonu.lteOnCdmaDevice=0
DEVICE_PROVISIONED=1
I: Checking for extendedcommand
I:Skipping for extendedcommand, file not found...
I:Can't partition non mmcblk device: /devices/platform/msm_sdcc.3/mmc_host/mmc1
I:using /data/media for /sdcard/0/clockworkmod/.no_confirm.
mount: mounting /dev/block/platform/msm_sdcc.1/by-name/userdata on /data failed: invalid argument
W:failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata (File exists)
I:using /data/media for /sdcard/0/clockworkmod/.many_confirm.
mount: mounting /dev/block/platform/msm_sdcc.1/by-name/userdata on /data failed: invalid argument
W:failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata (File exists)
I:Can't partition non mmcblk device: /devices/platform/msm_sdcc.3/mmc_host/mmc1
And here is the result of your command
Code:
C:\adt-bundle-windows-x86-20140321\adt-bundle-windows-x86-20140321\sdk\platform-
tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
YT910M7GB9 recovery
C:\adt-bundle-windows-x86-20140321\adt-bundle-windows-x86-20140321\sdk\platform-
tools>adb shell
~ # ←[6ncat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 3866624 mmcblk0
179 1 2048 mmcblk0p1
179 2 128 mmcblk0p2
179 3 256 mmcblk0p3
179 4 256 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 128 mmcblk0p8
179 9 256 mmcblk0p9
179 10 256 mmcblk0p10
179 11 512 mmcblk0p11
179 12 512 mmcblk0p12
179 13 512 mmcblk0p13
179 14 512 mmcblk0p14
179 15 512 mmcblk0p15
179 16 16384 mmcblk0p16
179 17 20480 mmcblk0p17
179 18 65536 mmcblk0p18
179 19 3072 mmcblk0p19
179 20 3072 mmcblk0p20
179 21 3072 mmcblk0p21
179 22 5120 mmcblk0p22
179 23 16384 mmcblk0p23
179 24 4096 mmcblk0p24
179 25 1228800 mmcblk0p25
179 26 256000 mmcblk0p26
179 27 2183151 mmcblk0p27
179 32 1955840 mmcblk1
179 33 1954816 mmcblk1p1
~ # ←[6nls -la /dev/block/mmcblk*
ls -la /dev/block/mmcblk*
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
brw------- 1 root root 179, 0 May 21 11:43 /dev/block/mmcblk0
brw------- 1 root root 179, 1 May 21 11:43 /dev/block/mmcblk0p1
brw------- 1 root root 179, 10 May 21 11:43 /dev/block/mmcblk0p10
brw------- 1 root root 179, 11 May 21 11:43 /dev/block/mmcblk0p11
brw------- 1 root root 179, 12 May 21 11:43 /dev/block/mmcblk0p12
brw------- 1 root root 179, 13 May 21 11:43 /dev/block/mmcblk0p13
brw------- 1 root root 179, 14 May 21 11:43 /dev/block/mmcblk0p14
brw------- 1 root root 179, 15 May 21 11:43 /dev/block/mmcblk0p15
brw------- 1 root root 179, 16 May 21 11:43 /dev/block/mmcblk0p16
brw------- 1 root root 179, 17 May 21 11:43 /dev/block/mmcblk0p17
brw------- 1 root root 179, 18 May 21 11:43 /dev/block/mmcblk0p18
brw------- 1 root root 179, 19 May 21 11:43 /dev/block/mmcblk0p19
brw------- 1 root root 179, 2 May 21 11:43 /dev/block/mmcblk0p2
brw------- 1 root root 179, 20 May 21 11:43 /dev/block/mmcblk0p20
brw------- 1 root root 179, 21 May 21 11:43 /dev/block/mmcblk0p21
brw------- 1 root root 179, 22 May 21 11:43 /dev/block/mmcblk0p22
brw------- 1 root root 179, 23 May 21 11:43 /dev/block/mmcblk0p23
brw------- 1 root root 179, 24 May 21 11:43 /dev/block/mmcblk0p24
brw------- 1 root root 179, 25 May 21 11:43 /dev/block/mmcblk0p25
brw------- 1 root root 179, 26 May 21 11:43 /dev/block/mmcblk0p26
brw------- 1 root root 179, 27 May 21 11:43 /dev/block/mmcblk0p27
brw------- 1 root root 179, 3 May 21 11:43 /dev/block/mmcblk0p3
brw------- 1 root root 179, 4 May 21 11:43 /dev/block/mmcblk0p4
brw------- 1 root root 179, 5 May 21 11:43 /dev/block/mmcblk0p5
brw------- 1 root root 179, 6 May 21 11:43 /dev/block/mmcblk0p6
brw------- 1 root root 179, 7 May 21 11:43 /dev/block/mmcblk0p7
brw------- 1 root root 179, 8 May 21 11:43 /dev/block/mmcblk0p8
brw------- 1 root root 179, 9 May 21 11:43 /dev/block/mmcblk0p9
brw------- 1 root root 179, 32 May 21 11:43 /dev/block/mmcblk1
brw------- 1 root root 179, 33 May 21 11:43 /dev/block/mmcblk1p1
~ # ←[6nmount
mount
rootfs on / type rootfs (rw,seclabel,relatime)
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)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,mode=050,gid=1028)
tmpfs on /mnt/secure type tmpfs (rw,seclabel,relatime,mode=700)
tmpfs on /mnt/fuse type tmpfs (rw,seclabel,relatime,mode=775,gid=1000)
/dev/block/platform/msm_sdcc.1/by-name/cache on /cache type ext4 (rw,seclabel,re
latime,data=ordered)
~ # ←[6nfdisk -l /dev/block/mmcblk0p17
fdisk -l /dev/block/mmcblk0p17
Disk /dev/block/mmcblk0p17: 20 MB, 20971520 bytes
4 heads, 16 sectors/track, 640 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p17 doesn't contain a valid partition table
~ # ←[6nfdisk -l /dev/block/mmcblk0p5
fdisk -l /dev/block/mmcblk0p5
Disk /dev/block/mmcblk0p5: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p5 doesn't contain a valid partition table
~ # ←[6n
C:\adt-bundle-windows-x86-20140321\adt-bundle-windows-x86-20140321\sdk\platform-
tools>

If both partitions are incorrect, should I try to flash?

[GENERAL][INFO] Mount Points for Xperia M

Hey guys,
Here is the mountpoint information for Xperia M I am still figuring out which of these goes for which partitions I will update if I find
Code:
PERM UID GID DATE PATH
lrwxrwxrwx root root 1970-07-11 15:19 FOTAKernel -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-07-11 15:19 LTALabel -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-07-11 15:19 TA -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-07-11 15:19 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-07-11 15:19 alt -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-07-11 15:19 boot -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-07-11 15:19 cache -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-07-11 15:19 fsg -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-07-11 15:19 modem -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-07-11 15:19 modemst1 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-07-11 15:19 modemst2 -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-07-11 15:19 persist -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-07-11 15:19 ramdump -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-07-11 15:19 rpm -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-07-11 15:19 s1sbl2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-07-11 15:19 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-07-11 15:19 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-07-11 15:19 sbl3 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-07-11 15:19 system -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-07-11 15:19 tz -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-07-11 15:19 userdata -> /dev/block/mmcblk0p27
Huge thanks to @mbc07
Code:
major minor #blocks name
179 0 3866624 mmcblk0
179 1 2048 mmcblk0p1
179 2 128 mmcblk0p2
179 3 256 mmcblk0p3
179 4 256 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 128 mmcblk0p8
179 9 256 mmcblk0p9
179 10 256 mmcblk0p10
179 11 512 mmcblk0p11
179 12 512 mmcblk0p12
179 13 512 mmcblk0p13
179 14 512 mmcblk0p14
179 15 512 mmcblk0p15
179 16 16384 mmcblk0p16
179 17 20480 mmcblk0p17
179 18 65536 mmcblk0p18
179 19 3072 mmcblk0p19
179 20 3072 mmcblk0p20
179 21 3072 mmcblk0p21
179 22 5120 mmcblk0p22
179 23 16384 mmcblk0p23
179 24 4096 mmcblk0p24
179 25 1228800 mmcblk0p25
179 26 256000 mmcblk0p26
179 27 2183151 mmcblk0p27
179 32 7822336 mmcblk1
179 33 7821312 mmcblk1p1

Just use ls -l /dev/block/platform/msm_sdcc.1/by-name
Layout:
Code:
PERM UID GID DATE PATH
lrwxrwxrwx root root 1970-07-11 15:19 FOTAKernel -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-07-11 15:19 LTALabel -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-07-11 15:19 TA -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-07-11 15:19 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-07-11 15:19 alt -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-07-11 15:19 boot -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-07-11 15:19 cache -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-07-11 15:19 fsg -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-07-11 15:19 modem -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-07-11 15:19 modemst1 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-07-11 15:19 modemst2 -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-07-11 15:19 persist -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-07-11 15:19 ramdump -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-07-11 15:19 rpm -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-07-11 15:19 s1sbl2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-07-11 15:19 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-07-11 15:19 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-07-11 15:19 sbl3 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-07-11 15:19 system -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-07-11 15:19 tz -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-07-11 15:19 userdata -> /dev/block/mmcblk0p27

Here you are a bit more information.
Also I have dumps of all these partitions and GPT backup.
If someone need to restore something – send PM (C1905 btw).
Code:
parted /dev/block/mmcblk0
print
Number Start End Size File system Name
1 131kB 2228kB 2097kB TA
2 2228kB 2359kB 131kB sbl1
3 2359kB 2621kB 262kB sbl2
4 2621kB 2884kB 262kB s1sbl2
5 2884kB 3408kB 524kB sbl3
6 3408kB 3932kB 524kB aboot
7 3932kB 4456kB 524kB tz
8 4456kB 4588kB 131kB alt_sbl1
9 4588kB 4850kB 262kB alt_sbl2
10 4850kB 5112kB 262kB alt_s1sbl2
11 5112kB 5636kB 524kB alt_sbl3
12 5636kB 6160kB 524kB alt_aboot
13 6160kB 6685kB 524kB alt_tz
14 6685kB 7209kB 524kB rpm
15 7209kB 7733kB 524kB alt_rpm
16 8389kB 25.2MB 16.8MB ext4 LTALabel
17 25.2MB 46.1MB 21.0MB boot
18 46.1MB 113MB 67.1MB fat16 modem
19 113MB 116MB 3146kB modemst1
20 117MB 121MB 3146kB modemst2
21 122MB 125MB 3146kB fsg
22 125MB 130MB 5243kB ramdump
23 130MB 147MB 16.8MB FOTAKernel
24 147MB 151MB 4194kB ext2 persist
25 151MB 1514MB 1363MB ext4 system
26 1514MB 1724MB 210MB ext4 cache
27 1724MB 3909MB 2185MB ext4 userdata
---------------
gdisk /dev/block/mmcblk0
p
Disk /dev/block/mmcblk0: 7733248 sectors, 3.7 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 98101B32-BBE2-4BF2-A06E-2BB33D000C20
Partition table holds up to 27 entries
First usable sector is 34, last usable sector is 7733214
Partitions will be aligned on 256-sector boundaries
Total free space is 103902 sectors (50.7 MiB)
Number Start (sector) End (sector) Size Code Name
1 256 4351 2.0 MiB FFFF TA
2 4352 4607 128.0 KiB FFFF sbl1
3 4608 5119 256.0 KiB FFFF sbl2
4 5120 5631 256.0 KiB FFFF s1sbl2
5 5632 6655 512.0 KiB FFFF sbl3
6 6656 7679 512.0 KiB FFFF aboot
7 7680 8703 512.0 KiB FFFF tz
8 8704 8959 128.0 KiB FFFF alt_sbl1
9 8960 9471 256.0 KiB FFFF alt_sbl2
10 9472 9983 256.0 KiB FFFF alt_s1sbl2
11 9984 11007 512.0 KiB FFFF alt_sbl3
12 11008 12031 512.0 KiB FFFF alt_aboot
13 12032 13055 512.0 KiB FFFF alt_tz
14 13056 14079 512.0 KiB FFFF rpm
15 14080 15103 512.0 KiB FFFF alt_rpm
16 16384 49151 16.0 MiB 8300 LTALabel
17 49152 90111 20.0 MiB FFFF boot
18 90112 221183 64.0 MiB 0700 modem
19 221184 227327 3.0 MiB FFFF modemst1
20 229376 235519 3.0 MiB FFFF modemst2
21 237568 243711 3.0 MiB FFFF fsg
22 243712 253951 5.0 MiB FFFF ramdump
23 253952 286719 16.0 MiB FFFF FOTAKernel
24 286720 294911 4.0 MiB 8300 persist
25 294912 2957311 1.3 GiB 8300 system
26 2957312 3366911 200.0 MiB 8300 cache
27 3366912 7634910 2.0 GiB 8300 userdata
---------------
gdisk /dev/block/mmcblk0
x
o
Disk size is 7733248 sectors (3.7 GiB)
MBR disk identifier: 0x00000000
MBR partitions:
Number Boot Start Sector End Sector Status Code
1 1 7733247 primary 0xEE
---------------
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 3959 MB, 3959422976 bytes
95 heads, 61 sectors/track, 1334 cylinders
Units = cylinders of 5795 * 512 = 2967040 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 1335 3866623+ ee EFI GPT
---------------
df
Filesystem Size Used Free Blksize
/dev 430.6M 128.0K 430.4M 4096
/sys/fs/cgroup 430.6M 12.0K 430.5M 4096
/mnt/asec 430.6M 0.0K 430.6M 4096
/mnt/obb 430.6M 0.0K 430.6M 4096
/mnt/fuse 430.6M 0.0K 430.6M 4096
/system 1.3G 374.4M 907.4M 4096
/data 2.0G 1.5G 555.2M 4096
/cache 197.0M 68.2M 128.8M 4096
/persist 3.9M 84.0K 3.8M 4096
/lta-label 15.8M 4.1M 11.7M 4096
/firmware 64.0M 44.1M 19.9M 16384
/mnt/shell/emulated 2.0G 1.5G 555.2M 4096
/storage/emulated/legacy 2.0G 1.5G 555.2M 4096
/mnt/media_rw/sdcard1 14.8G 11.6G 3.3G 8192
/storage/sdcard1 14.8G 11.6G 3.3G 8192
---------------
mount
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/userdata /data ext4 rw,seclabel,nosuid,nodev,relatime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime 0 0
/dev/block/platform/msm_sdcc.1/by-name/LTALabel /lta-label ext4 ro,seclabel,nosuid,nodev,noexec,noatime,nobarrier,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/vold/179:33 /mnt/media_rw/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,cod
epage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/sdcard1 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0

Difficulty extracting recovery partition from F460

EDIT: oops problem solved using carliv image kitchen
I'm completely at a loss here trying to just make an image or mount the stock recovery partition on the F460 variant. Much thanks to anyone who looks at this...
I did the standard dd to img file and I can't open it, getting a bunch of errors (see below) when run through various disk tools. I tried to dd the exact block range which just produces the same result.
I tried mounting the recovery partition on the device but mount doesn't want to work with me.
Code:
1|[email protected]:/ # mount /dev/block/mmcblk0p21 /sdcard/recovery
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|[email protected]:/ # mount -t ext4 /dev/block/mmcblk0p21 /sdcard/recovery
mount: Invalid argument
I booted into recovery from ADB just to see if it was even intact and it showed the stock recovery logo just fine.
Here's some (helpful??) details...
Code:
[email protected]:/ $ cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 87536 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 512 mmcblk0p3
179 4 16 mmcblk0p4
179 5 512 mmcblk0p5
179 6 2048 mmcblk0p6
179 7 1024 mmcblk0p7
179 8 1024 mmcblk0p8
179 9 4 mmcblk0p9
179 10 1024 mmcblk0p10
179 11 512 mmcblk0p11
179 12 1024 mmcblk0p12
179 13 1024 mmcblk0p13
179 14 1024 mmcblk0p14
179 15 1024 mmcblk0p15
179 16 512 mmcblk0p16
179 17 2048 mmcblk0p17
179 18 2044 mmcblk0p18
179 19 16384 mmcblk0p19
179 20 32768 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 1024 mmcblk0p22
179 23 1024 mmcblk0p23
179 24 1024 mmcblk0p24
179 25 1 mmcblk0p25
179 26 4 mmcblk0p26
179 27 3072 mmcblk0p27
179 28 512 mmcblk0p28
179 29 512 mmcblk0p29
179 30 4 mmcblk0p30
179 31 512 mmcblk0p31
259 0 512 mmcblk0p32
259 1 8 mmcblk0p33
259 2 5104 mmcblk0p34
259 3 16384 mmcblk0p35
259 4 8192 mmcblk0p36
259 5 8192 mmcblk0p37
259 6 32768 mmcblk0p38
259 7 32768 mmcblk0p39
259 8 32768 mmcblk0p40
259 9 32768 mmcblk0p41
259 10 2523136 mmcblk0p42
259 11 868352 mmcblk0p43
259 12 16384 mmcblk0p44
259 13 26480640 mmcblk0p45
259 14 188399 mmcblk0p46
179 32 4096 mmcblk0rpmb
179 64 30703616 mmcblk1
179 65 30702592 mmcblk1p1
Code:
[email protected]:/ $ ls -al /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root root 1970-01-04 01:47 DDR -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-04 01:47 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-04 01:47 abootb -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-04 01:47 boot -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-04 01:47 cache -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 1970-01-04 01:47 drm -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-04 01:47 eksst -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-04 01:47 encrypt -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-04 01:47 factory -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-01-04 01:47 fota -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-01-04 01:47 fsc -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-04 01:47 fsg -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-04 01:47 grow -> /dev/block/mmcblk0p46
lrwxrwxrwx root root 1970-01-04 01:47 laf -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-01-04 01:47 mdm1m9kefs1 -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-04 01:47 mdm1m9kefs2 -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-04 01:47 mdm1m9kefs3 -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-04 01:47 mdm1m9kefsc -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-04 01:47 misc -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-04 01:47 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-04 01:47 mpt -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-01-04 01:47 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-04 01:47 pad1 -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-04 01:47 pad2 -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-04 01:47 persist -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-04 01:47 rct -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-04 01:47 recovery -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-04 01:47 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-04 01:47 rpmbak -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-04 01:47 rpmf -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-04 01:47 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-04 01:47 sbl1b -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-04 01:47 sdi -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-04 01:47 sdibak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-04 01:47 sdif -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-04 01:47 sec -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-04 01:47 sns -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-01-04 01:47 spare1 -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-04 01:47 spare2 -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-04 01:47 spare3 -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 1970-01-04 01:47 ssd -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-04 01:47 system -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-01-04 01:47 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-04 01:47 tzbak -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-04 01:47 tzf -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-04 01:47 userdata -> /dev/block/mmcblk0p45
Code:
[email protected]:~/Desktop$ parted recovery.img
WARNING: You are not superuser. Watch out for permissions.
GNU Parted 2.3
Using /home/shawn/Desktop/recovery.img
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
Error: /home/shawn/Desktop/recovery.img: unrecognised disk label
[email protected]:~/Desktop$ fdisk -l recovery.img
Disk recovery.img: 16 MB, 16777216 bytes
255 heads, 63 sectors/track, 2 cylinders, total 32768 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk recovery.img doesn't contain a valid partition table
[email protected]:~/Desktop$ e2fsck recovery.img
e2fsck 1.42.9 (4-Feb-2014)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open recovery.img
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>
[email protected]:~/Desktop$ e2fsck -b 8192 recovery.img
e2fsck 1.42.9 (4-Feb-2014)
e2fsck: Attempt to read block from filesystem resulted in short read while trying to open recovery.img
Could this be a zero-length partition?

Pushing a ROM.zip file always fails to complete to 100%

I am using a Linux machine and adb.
Nubia NX503a (25S)
Code:
[email protected]:~$ adb devices
List of devices attached
MSM8974 recovery
[email protected]:~$
Code:
~ # ls -la
drwxr-xr-x 22 root root 0 Jan 3 18:48 .
drwxr-xr-x 22 root root 0 Jan 3 18:48 ..
drwxr-xr-x 2 root root 0 Jan 3 18:46 boot
drwxr-xr-x 4 root root 4096 Jan 3 18:03 cache
drwxr-xr-x 5 root root 4096 Jan 3 20:15 data
drwxr-xr-x 2 root root 0 Jan 3 18:46 datadata
-rw-r--r-- 1 root root 5785 Jan 1 00:00 default.prop
drwxr-xr-x 10 root root 15160 Jan 3 18:46 dev
drwxr-xr-x 2 root root 0 Jan 3 18:46 emmc
drwxr-xr-x 2 root root 0 Jan 3 18:46 etc
drwxr-xr-x 2 root root 0 Jan 3 18:46 external_sd
-rwxr-x--- 1 root root 113592 Jan 1 00:00 init
-rwxr-x--- 1 root root 1417 Jan 1 00:00 init.rc
drwxr-xr-x 2 root root 0 Jan 3 18:46 internal_sd
drwxrwx--x 6 system system 4096 Jan 2 00:30 persist
dr-xr-xr-x 158 root root 0 Jan 1 00:00 proc
drwxr-xr-x 2 root root 0 Jan 3 18:46 recovery
drwxr-xr-x 3 root root 0 Jan 1 00:00 res
drwx------ 2 root root 0 Dec 30 2013 root
drwxr-x--- 2 root root 0 Jan 1 00:00 sbin
drwxr-xr-x 2 root root 0 Jan 3 18:46 sd-ext
drwxrwxrwx 2 root root 8192 Jan 1 00:00 sdcard
dr-xr-xr-x 15 root root 0 Jan 3 18:46 sys
drwxr-xr-x 16 root root 4096 Jan 1 00:00 system
drwxrwxr-x 2 root shell 0 Jan 3 18:46 tmp
-rw-r--r-- 1 root root 272 Jan 1 00:00 ueventd.goldfish.rc
-rw-r--r-- 1 root root 5897 Jan 1 00:00 ueventd.rc
~ #
It can be seen that the sdcard is 0% used:
Code:
~ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 924.0M 48.0K 924.0M 0% /dev
/dev/block/platform/msm_sdcc.1/by-name/cache
492.6M 8.7M 483.9M 2% /cache
/dev/block/platform/msm_sdcc.1/by-name/userdata
2.5G 424.5M 2.0G 17% /data
/dev/block/platform/msm_sdcc.1/by-name/grow
9.8G 8.0K 9.8G 0% /sdcard
/dev/block/platform/msm_sdcc.1/by-name/system
1.2G 485.0M 726.5M 40% /system
/dev/block/platform/msm_sdcc.1/by-name/persist
4.9M 4.1M 812.0K 84% /persist
~ #
The sdcard:
Code:
~ # cat /proc/partitions
major minor #blocks name
179 0 15388672 mmcblk0
179 1 65536 mmcblk0p1
179 2 512 mmcblk0p2
179 3 32 mmcblk0p3
179 4 32 mmcblk0p4
179 5 512 mmcblk0p5
179 6 500 mmcblk0p6
179 7 10240 mmcblk0p7
179 8 500 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 1536 mmcblk0p10
179 11 1536 mmcblk0p11
179 12 1024 mmcblk0p12
179 13 10240 mmcblk0p13
179 14 1258290 mmcblk0p14
179 15 2621440 mmcblk0p15
179 16 32768 mmcblk0p16
179 17 512000 mmcblk0p17
179 18 153600 mmcblk0p18
179 19 10240 mmcblk0p19
179 20 1536 mmcblk0p20
179 21 1 mmcblk0p21
179 22 8 mmcblk0p22
179 23 10276838 mmcblk0p23
179 32 4096 mmcblk0rpmb
~ #
Is 179 23 10276838 mmcblk0p23, but I forget how I linked the sdcard to mmcblk0p23
Using:
adb push -p /home/makem/Downloads/update2.zip /dev/block/mmcblk0p23/update2.zip
or
adb push -p /home/makem/Downloads/update2.zip /data/media/update2.zip
or
adb push -p /home/makem/Downloads/update2.zip /sdcard/
Each fail by stopping anywhere between 5% and 47%. I have wiped the cache, data and delvik cache prior to pushing.
When I check the sdcard again with df I find it is still at 0%, except for the last push which stopped at 10% and showed 1% used sdcard.
EDIT: After the last push the file update2.zip showed in the sdcard when I went to install it. However, it stopped with a 'bad' error. Obviously an incomplete upload but why????
Tearing my hair out here lol.