Most probably.
Not easily at least. But since the biggest problem is the missing backup of the complete data partition (OS install files can be downloaded and kept to get the other partitions into the desired state again) you may want to have a look at Android Backup and Restore Tools (ABRT) …
I am in the process of moving my devices away from /e/OS to LineageOS for microG. As part of this process I did quite a lot of work backing up my user-installed apps and my setting, then restoring / migrating them to new ROMs and to different devices. In fact, I didn’t need the backups: once I had the new ROMs built correctly, I was able to successfully ‘dirty flash’ them over my existing custom /e/OS builds. But I tried anyway, to get some up-to-date experience of which solutions work best.
It really isn’t (so long as you have access to a computer or VM running linux). You just
download this zip file ,
unzip it, which wll create a directory called android-backup-project-v2.1
cd to the android-backup-project-v2.1 directory
connect your device
run adb devices to check the device is properly connected
run adb root to check that rooted debugging is enabled on the device
run the backup_apps.sh script
wait for it to complete
This tool shuts the device down, then restarts it runni…
… or this here …
I searched a lot and I found a way to do the backup using root adb. I could get a full backup of the data using this command on the computer on which the phone is pluged:
adb root > /dev/null && rsync -a --delete --rsh="adb" shell:/data/data/ /mnt/home/almtesh/Temporaire/Pledge/e/data/
Yes, I know I should do adb unroot when done, but I don’t want scrcpy to be terminated at each backup.