'dd' backup fails

General
#1

Following the guide in the top of the answer:

https://together.jolla.com/question/81832/full-phone-backup-guide/

The dd command only backs up 1MB then exits. Using 4.1 on phone and recovery on XA2. Output as follows:

If you continue, this may void your warranty. Are you really SURE? [y/N] y
/dev/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input/output error
/dev/mmcblk0rpmb: read failed after 0 of 4096 at 4128768: Input/output error
/dev/mmcblk0rpmb: read failed after 0 of 4096 at 4186112: Input/output error
/dev/mmcblk0rpmb: read failed after 0 of 4096 at 4096: Input/output error
2 logical volume(s) in volume group “sailfish” now active
Thu Jan 13 01:24:42 UTC 2022

Type your devicelock code and press [ENTER] key:
(please note that the typed numbers won't be shown for security reasons)
[OK] Code accepted.
/ # mkdir -p /mnt/BackupCard
/ # mount /dev/mmcblk1p1 /mnt/BackupCard/
/ # dd if=/dev/mmcblk0p28 of=/mnt/BackupCard/jolla-fullBackup-p28.img
2048+0 records in
2048+0 records out
1048576 bytes (1.0MB) copied, 0.028175 seconds, 35.5MB/s
#2

Are you sure mmcblk0p28 is where your data is? That guide is pretty old - fs structure might be different… Try to find where in /dev your partitions are, probably something like /dev/block/platform/soc/1d84000.ufshc/by-name (that’s mine - yours is probably different, but probably somewhere down /dev/block/platform…)

Then run ls -al /dev/block/platform/soc/1d84000.ufshc/by-name (or whatever)

and look for userdata, and see if it’s actually mmcblk0p28

2 Likes
#3

mmcblk0p76!

I have ~40 partitions (?) in there, is that normal? :wink:

1 Like
#4

On XA2 (with 4.3 at least), you have to backup partition #76.
I did it as proposed by DrYak in the [xa2] Full-backup in terminal thread (click “see more comments” near the end)).
Restoring it perfectly works except fingerprints as in Backup/Restore, where are fingerprints stored?, because I restored on another device. (and maybe wifi, I don’t remember).

EDIT: Reflash the same OS as the backup was made on before to restore, to be sure every other partition is ok too.

I also had

/dev/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input/output error
/dev/mmcblk0rpmb: read failed after 0 of 4096 at 4128768: Input/output error
/dev/mmcblk0rpmb: read failed after 0 of 4096 at 4186112: Input/output error
/dev/mmcblk0rpmb: read failed after 0 of 4096 at 4096: Input/output error

even after having reslashed Android, then SFos, then boot in recovery mode.
Any idea if it is a problem?

1 Like
#5

Seems consistent since 3.3 or so. The guide you linked to was April 2019. Wonder if we could make an easily-findable guide.

I also had
/dev/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input/output error

I assumed it was a failure to read the encrypted partition. It asks for the key after.