Meaning: every time you screw up (or get a new phone) you have to start all over, without the ability to restore a backup.
This can easily take many days worth of man-hours.
Source: I've tried.
Meaning: every time you screw up (or get a new phone) you have to start all over, without the ability to restore a backup.
This can easily take many days worth of man-hours.
Source: I've tried.
The backup problem is a notorious problem with any Android phone, I don't understand what it has to do with custom ROMs.
As for backup: stock backup facilities (adb backup/restore) aren't exactly the best thing for sure, (rip Titanium Backup, Seedvault isn't even remotely there), and TWRP is broken on most of devices with modern encryption support (specifically, on Pixels). Coincidentally, Mediatek SoC based devices are the 'best' when talking about backup (as in: you can dump and clone all partitions through a built-in service mode [1]).
0. https://sourceforge.net/projects/andyyan-gsi/files/ 1. https://github.com/bkerler/mtkclient
If I don't feel confident I'll be able to get a custom ROM working on my phone I'll have 2nd thoughts about erasing the original ROM
> there's no way to take full backups on Android phone, rooted or not
Er, no? On the contrary, root is exactly how you get full backups on Android - with, I grant, the exception of whatever Android calls their secure element / TPM, which I've only ever seen affect 2FA apps.