Feature #1802
openReplicant 6.0 recovery lacks backup features
0%
Description
Hi,
Replicant 4.2 recovery could:- Backup the system
- Restore the system
Replicant 6.0 recovery is however needed to install replicant 6.0.
Rationale:- In the case where the users wants to backup their device running replicant 4.2 before installing replicant 6.0, they have to first make sure that the old 4.2 recovery is installed, then to backup with it, and then to reflash the 6.0 recovery and install replicant with that.
- On devices unsuported by replicant 4.2 like the i9305, no 4.2 recovery are available, so there are no way to make backups with the recovery.
- Having to handle two backup images is way more complicated and error-prone
Denis.
Updated by Wolfgang Wiedmeyer almost 7 years ago
Using the backup functionality from the recovery for backup and restore after upgrading to Replicant 6.0 is very likely a bad idea anyway. There are incompatibilities between the databases which e.g. cause issues with the SMS app, clock app and others.
I already addressed this on the general usage page.
It's generally better to do a selective backup (e.g. with oandbackup) to avoid such issues, so I'm not sure if this feature is really needed. It could cause more harm than good if users count on it and it fails because such incompatibilities can happen.
Updated by Wolfgang Wiedmeyer almost 7 years ago
- Tracker changed from Issue to Feature
Updated by Denis 'GNUtoo' Carikli almost 7 years ago
The idea here is to allow to backup the existing operating system that works (whatever that is) before the user tries Replicant.
Many users are afraid of trying Replicant, and they are unsure if it will work fine or not.
The installation instructions should also then probably reflect that and provide a way to backup the existing system (which could also be Replicant 4.2).
Updated by Wolfgang Wiedmeyer almost 7 years ago
Denis 'GNUtoo' Carikli wrote:
The idea here is to allow to backup the existing operating system that works (whatever that is) before the user tries Replicant.
Many users are afraid of trying Replicant, and they are unsure if it will work fine or not.
The installation instructions should also then probably reflect that and provide a way to backup the existing system (which could also be Replicant 4.2).
I see. The instructions currently also flash the recovery image to the boot partition, so I imagine that a full backup doesn't work because the kernel of the previously installed system can't be backed up. With the Galaxy S2 and Galaxy Note, the recovery has to be flashed to the kernel partition because there is no separate recovery partition that the bootloader can load and boot on its own.
adb backup should still work with the recovery. Backing up and restoring with ADB could be tested first, so we have at least this as an option.