Actually it is in /e/, but it’s not yet visible in the phone UI. This thread describes how you can use it via `adb’ on a connected computer
Also, if you have access to a linux computer, then this post suggests a possible alternative backup solution
Actually it is in /e/, but it’s not yet visible in the phone UI. This thread describes how you can use it via `adb’ on a connected computer
Also, if you have access to a linux computer, then this post suggests a possible alternative backup solution
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.
EDIT: I tried to crop this pic but the Gallery app essentially gets stuck processing. That’s not cool.
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.
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 partitionThanks for this complete review !
AFAIK installing TWRP on the phone does wipe all data.
How did you solve that?
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?
See the reply from @AnotherElk
All of my phones have TWRP installed on the recovery partition. More recent phones apparently d things differently, but I know very little about that
Yes. But …
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?”
I guess because
Because I have never known installing TWRP to cause loss of data. Unlocking bootloader will cause loss of data, but that is not covered by this tutorial.
What steps did you follow to flash TWRP. What device are you using?
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
Interesting. I can confirm that the current TWRP 3.6.2_9-0-FP3 using MTP offers no change timestamps. I’m using Windows 11 Pro on the computer side.
And apparently this isn’t entirely new, although seemingly dependent on the device or on the computer OS … https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1065
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.
I must admit, I’m not shure if it worked with my /e/-installation.
It works with my Lineage-install. I’m using it regularly to synchronize files between my FP3 and Win10(pro)-Computer. Should work for /e/ just the same - a lineage-fork - isn’t it
actual IMG-e-1.2-r-20220727206630-dev-FP3 I tested bases on lineage 18.1
I actually use latest 18.1-package
lineage-18.1-20220620-nightly-FP3-signed.zip
Thanks for your answer. Stepped away from the forum for some days Aehm. I do not know exactly anymore which steps I followed, but mostly internal documentation about TWRP and unlocking the bootloader. Maybe XDA too. Should have read this first “✏ FP3: unlock the bootloader - Guides - Fairphone Community Forum”
I’m using the Fairphone 3.
So, used the wipe to flash Android 11. But now my build-number seems suspect to me: “eng.root (…) dev-keys” is not what I wanted. Bootloader is locked, but SafetyNet is not working anymore, CTS profile does not match.
I’m using the Fairphone 3.
So, used the wipe to flash Android 11. But now my build-number seems suspect to me: “eng.root (…) dev-keys” is not what I wanted.
Android 11 (R) currently is only available on the dev release channel, still marked as beta …
https://images.ecloud.global/dev/FP3/
https://images.ecloud.global/stable/FP3/
You can compare these download filenames most easily to Settings - About phone - Android version (tap on it) - /e/OS version (it has the same version string format).
SafetyNet is not working anymore, CTS profile does not match.
With the update to 1.0 it was announced that SafetyNet would pass on stable devices. Sadly, my FP3 with 1.0-q-dev does not pass. I’m not complaining, since I’m not actually on the stable branch, but I wonder: What is the big difference between the stable and dev release for the same device that makes SafetyNet fail on dev although it works on stable? Regain your privacy! Adopt /e/ the unGoogled mobile OS and online services[phone]
Thank you for digging those posts! I had no luck with my keywords Seems like, I need to reflash or do you think there might be a chance, that once Android 11 is out of beta, my build-number gets “stable”?
Seems like, I need to reflash or do you think there might be a chance, that once Android 11 is out of beta, my build-number gets “stable”?
You will need to reinstall for stable. The dev beta will just stay dev once out of beta.
Changing the release channel is always a new install.
But you can only install Android 10 (Q) currently as stable. An OTA upgrade to Android 11 (R) is just announced without a timeline, until then upgrading to Android 11 (R) would be a new install again.
OS OTA upgrades
Status: in Progress
[…]
Upcoming[…]
- FP3
- ETA not available
- Will be planned after the release of the s8/s8+ OS OTA upgrade