chaosmaster / android_device_fairphone_fp3 Goto Github PK

Hello,
I want to install twrp-3.7.0_12 permanently on my FP3 (/e/OS-S-dev rooted with Magisk) as is with v3.7.0_9.

I did as usual: boot twrp.img and then try to use Flash Current TWRP. But that throws and error that the ram disk has been changed and twrp cannot write to it.
Is that normal for this build?
So I used the alternate way Install Recovery Ramdisk. Afterwards I rebooted to recovery and v3.7.0_12 was installed. But booting to system does not work any more. The phone always boots to recovery.

Installing the previous boot.img (twrp-3.7.0_9 patched with Magisk) solved the issue and I can boot to system again.

What might cause the issue? Is there something wrong

• with the TWRP build?
• the /e/OS build?
• or is the reason for the loop to recovery that Magisk app is still installed but of course the boot image is not yet rooted again at the first reboot to system?

What is missing to bring this TWRP recovery to https://twrp.me/Devices/?

[Obsolete]

Just pulled twrp-3.3.1-0_k4y0z-20200202-02-fp3.img and did a fastboot boot twrp-3.3.1-0_k4y0z-20200202-02-fp3.img
Done on a macos using
fastboot version 29.0.5-5949299
Installed as /usr/local/bin/fastboot

results in
Sending 'boot.img' (28690 KB) OKAY [ 0.644s]
Booting OKAY [ 8.662s]
Finished. Total time: 9.392s

However when it boots, I get a white screen with grey streaks that shift around. Guessing it looks like a video output format issue, but I've not seen this on an Android TWRP before.

I'm able to do a long press power down and reboot it back into the OS, but only after a bit of repetition.

The new version 3.6.1 is not available for Fairphone 3 because the builds fail according to https://jenkins.twrp.me/

Is there anything you can do about it?

I'm on Fairphone 3+, OS version 0023.0, Android 11

I booted on twrp-3.7.0_12-0_k4y0z-20230821-01-fp3.img via adb, which didn't work of course for decryption (wrong OS version)

Then I booted on twrp-3.7.0_11-0_k4y0z-20230818-01-fp3.img which worked fine, acccessed partitions, and backed up everything.

But then, back to system, Settings app and bluetooth kepts crashing, lots of tracebacks in the logcat, telling that eg. /data/user_de/0/com.android.settings/databases/homepage_cards.db was not found (and indeed /data/user_de/0/com.android.settings does not exist at all).

It's a similar problem as : https://community.e.foundation/t/settings-stop-working/46072/9 (in that it's due to TWRP, not in the precise diagnostic)

I have no idea if it's the 12 or the 11 image boot that broke my system.

But I didn't expect a "backup" operation to alter and break my system folders, it's weird.

Hello,
the official TWRP is in the Android 9 branch and does not support data encryption if Android 12 is installed.
Does the Android 12 release in this repo support data encryption?