For my FP3 it is said that unlocking may disrupt data - this is the reason Iâd like to make a backup using TWRP in temporary mode.
So far I am hindered to do that out of reasons I do not understand.
Kind of a vicious circle, as I want to avoid to brick itâŚ
Oh, I see now.
To reach a state in which I can backup my data I have to wipe it out first.
This seems kinda semi-nice.
On my desktop I have system & data encrypted. So, if anyone accesses the computer, still the passphrase is needed to get hold of any data.
A mandatory wiping out may be useful in case you have a recent backup.
As long as you donât, I have to cite myself:
So far there is not much on the phone to store away since I have it only three months now, just the present state of contacts, some msgs and logs.
As installing of TWRP wipes any data anyway I might
unlock the bootloader
install it to the disc
relock the bootloader (?)
restore saved data
go on with nandroid
Is that a fair plan?
BTW, why doesnât come it with TWRP in the first place?
Because TWRP is a separate project, might not have support for the same devices as /e/OS and is outside of direct control of /e/OS developers in case something would need fixing. I guess.
Depends on whether /e/OS even boots with TWRP installed (= altered boot partition) after locking the bootloader ⌠and on whether you can get TWRP retained through OS updates via rooting with Magisk, as otherwise /e/OS updates will restore the boot partition to the intended state including the /e/OS recovery.
I donât have answers to this on hand immediately, but a forum search should bring them up.
Personally Iâm running an unlocked bootloader (after careful risk assessment regarding my situation), and just boot TWRP temporarily when I want to use it.
Not if you planned for this from the start.
But in hindsight you are right.
@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âŚ
@manoj,
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?
Thank you
In /e/OS v1.0 R (on Teracube) I see Seedvault is present. Is it functional in this case?
Havenât tried it yet. Tried to use it once or twice on another phone and ROM. Didnât care for its limitations regarding restoration but maybe Iâll take another look.
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.
Results
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
SeedVault
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)
Conclusions
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
It hasnât been pointed out clearly enough, but it turns out that you can boot TWRP with fastboot, but you shouldnât install it on devices like FP3.
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.
So, just booting TWRP into fastboot mode on my FP3 gives the opportunity to backup without installing, if I understand the advice here.
Is that correct?