Please also note that Android security features like AVB (Android Verified Boot) & dm-verity might make your device unbootable if you tamper with some partitions. Keep your important data always backed up off-device!
Correct, encrypted userdata is forced on new devices, so for accessing Android userdata TWRP is currently not useful.
There’s some TWRP support for this feature and I’ll look into getting it working reliably on FP4, maybe for the next build
I wouldn’t recommend it, encrypted /data is default on newer Android versions I believe.
If you do, you will have to wipe the data partition completely and I wouldn’t try that without a complete flashable rom available for disaster recovery.
Hey,
since I flashed /e/os on my FP4, I cant boot into twrp anymore.
Any ideas, why this is the case?
I would like to use TWRP to root my device using Magisk, since the usual method doesnt work on /e/os
Because installing /e/ overwrites the recovery partitions
And besides, please don’t flash TWRP to your device, just boot it with fastboot boot twrp.img
What problems do you have with the usual way, it apparently still works
Edit: To be slightly more precise, since you are flashing your whole phone anyway, you can just take the boot.img from the /e/ release, patch that with Magisk and flash it to your device. If you need help with that, please head over to the root topic
Using Magisk to flash the Stock ROM boot.img works fine. I did that, when /e/os was not released yet. It doesnt work with the /e/os provided boot.img. Many guides in their forum suggested to use TWRP instead to flash the Magisk.zip directly, since it doesnt require to modify the boot.img using the install step.
I did not try to flash it. I tried to boot it using fastboot boot downloaded-twrp-name-that-is-really-long.img, however it stayed in the boot screen where it showed “Fairphone”.
Have you tried flashing a modified boot.img with fastboot? Flashing Magisk through TWRP will modify the boot.img anyway. Could you maybe link one of their guides, I don’t really get the point.
Ah, sorry, misunderstood you there
Someone with /e/ actually running will have to test if booting TWRP still works…
@hirnsushi send me a boot img. And it worked (at least magisk shows that its installed), when I flashed it.
However, a direct install still doesnt work. Its really odd.
After the initial install of /e/os, what did you do? I only locked the critical bootloader again. Do you think that may be a reason?
I downloaded the e/os zip, patched the boot.img and then just followed the regular installation instructions with the patched boot.img. I also didn’t locked the bootloader after that
Edit: Meaning I just did this
Boot your FP4 in bootloader mode, and plug it to your computer
On your computer, download the zip file from the link provided above. Unzip the folder and browse into it
Flash /e/ with the following commands:
with the patched boot.img instead of the regular one
Interesting. Did you unlock your bootloader (again) before the install?
As my phone was already unlocked, I skipped it and only unlocked the critical part.
I didn’t unlock anything specifically for e/os, I’d already unlocked everything I needed to flash a rooted stock image about a week ago. I didn’t change anything since then
You won’t be able to backup the whole device until there’s a version with support for encrypted 
Flashing Magisk through TWRP will modify the boot.img anyway. Could you maybe link one of their guides, I don’t really get the point.
