@AnotherElk: No, I didn’t plan so far, just checked the opportunities.
I had a FP2 a few years ago that was rooted and had TWRP running. As things change very fast these days and forum entries sometimes vary in relevance and reliability, I am a little lost.
I think I wait on the OS-update that is quite overdue.
If this doesn’t solve it, I should think about rooting the thing and putting TWRP and a working OS on it.
@petefoth: As it is getting worse by the hour, I’m afraid that’s impossible.
Meanwhile I do not get no Internet connection anymore, neither through LTE nor WLAN. Even flight mode on/off doesn’t change anything.
So, no installing, no testing.
Worse: My corona contact tracing app - one of my main reasons for using a “smartphone” - doesn’t work anymore, for regardless of Bluetooth working, it needs DNS to check for threat-updates through synchronising with the database.
I keep thinking that my old brick (a waterproof and shock-resistant Hammer 3+ with some kind of OpenBSD on it) was in fact smarter than the FP3 on /e, for it got DNS anytime, provided a hotspot and did not talk to strangers; but no chance for apps…
If i have an old.android from which i want to retain certain personal data via TWRP (e.g. brave browser instances that do not copy over without getting deep inside the phone) before i discontinue using it, but my new phone is not of the same brand/model, then have you suggestions for which particular folders are eapecially relevant or IRrelevant?
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.
TWRP backup of data partition
All user installed apps, with all their data. Ignores the ‘Backup not allowed’ flag
‘All or nothing’ not possible to restore individual apps
Successfully restored / migrated: to a new ROM on same device, to different devices (by copying the backup from one device to another)
Most apps and most of their data backed up. Ignores the ‘Backup not allowed’ flag
Some apps lose their data, particularly those that store acount data in Account Manager. For these apps, you will need to re-enter account details in the app, or create new accounts in Account Manager
Some apps keep stopping after restore / migrate. Can be fixed by clearing storage. Affected apps for me are: OS Maps, Element
Can restore specific apps, without affecting other apps
Respects the ‘Backup not allowed’ flag, so some apps will not be backed up at all, or will be backed up but with no data. You will need to install them, and set them up from scratch. These include BBC Sounds, News, Sport & Weather, Ebay, Element, WhatsApp, Garmin Connect, Twidere, Messenger, Magic Earth, OpenKeychain, Telegram FOSS
Does not backup settings for some apps (e.g. Lawnchair)
Some apps which claim to have been restored, don’t actually start (BRS Golf, XDA Forums)
If it works for your use case, then TWRP backup / restore of data partition is the most effective at duplicating your current setup on your new ROM or your new device. (In this case, there’s a good chance that ‘dirty flashing’ will also work, and the backup won’t be needed. Worth doing though, just in case )
If you have a computer (or a VM) running Linux, and your device / ROM supports rooted debugging (i.e. it’s not a stable /e/OS build), then ABRT is nearly as good. It has the advantage of working with individual apps rather than with the entire data partition
SeedVault is really limited, and only fit for use if no other alternative exists for your ROM / device. After restoring / migrating, you will need to test the apps that claim to have been backed up, an reinstall any that don’t actually work
Installing TWRP doesn’t wipe user data.
Unlocking the bootloader does, if you need to unlock it to install TWRP, which isn’t necessarily the case (if the bootloader already is left unlocked or can’t be locked).
In general, just refer and stick to the documentation at twrp.me for a specific device to know the TWRP proceedings on this device.
hooray. Just wiped my phone, trying to flash twrp. I knew I should save my pictures first, but I thought I will backup my pictures afterwards, bc I’m just trying to install the Backupstuff. Very pissed right now.
Why does this Tutorial not start with, “you’ll wipe your data if you try to flash TWRP?”
on devices where true would need active running of wipe command by user or user consent to wipe, as far as I understand. (Or does locking/unlocking the bootloader not ask for consent for the included factory reset? I don’t remember, unfortunately.)
because until now apparently nobody added something like this to the tutorial. It’s a Wiki post, feel free to, “Edit” button at the bottom right of the tutorial post.
Files I copied from TWRP MTP mode all got the same timestamp something in 1970 - unusable for backup of only changed files - like I do with FreeFileSync with device connected via USB
I got twrp-installer-3.5.2_9-0-FP3 installed
actually the only reliable tool I’ve got is Titanium - up till now only Signal didn’t work after recovering
I just asked the TWRP maintainer for Fairphone 3/3+ … let’s see.
FreeFileSync got that working reliably? There were a bunch of MTP problems reported in the past.
Anyway, doing this sync with /e/OS booted is not an option (since you mentioned Titanium)? The timestamps are there when /e/OS does MTP.