I'm considering to root my Fairphone 3 running Android 13 on /e/OS (a close Lineage OS derivative). However, I don't wish to wipe my data by unlocking the bootloader, so I had the following idea to circumvent it: 1. On [the official download site](https://images.ecloud.global/stable/FP3) , find the link of the update file named IMG-e-2.4.1-t-official-FP3.zip (may contain additional numbers) and remove the string IMG from the address. Download the file. 2. Extract the boot.img from the e-2.4.1-t-official-FP3.zip. 3. Patch the boot.img with Magisk. 4. Inside the e-2.4.1-t-official-FP3.zip, replace the official boot.img with the Magisk-patched one. 5. Go to settings ➡️ updater ➡️ “apply local update”, and select the patched e-2.4.1-t-official-FP3.zip. Could anything unintended happen if I just ignored the vbmeta.img that is also present in e-2.4-t-official-FP3.zip? (I hesitate to install Magisk [via recovery](https://topjohnwu.github.io/Magisk/install.html#custom-recovery) , because it's not recommend on modern devices. Feel free to correct me if that method is still safe on my device.) I foresee three possible error scenarios: - Android recognises the e-2.4-t-official-FP3.zip as “corrupted” and refuses to update. - Android does not refuse to apply the update, but fails to flash the boot partition due to the locked bootloader, possibly bricking the device. - While updating, Android automatically unlocks the bootloader to flash the boot partition, wiping my data without prior notice. What will happen? Should I just try it? Please note that various /e/OS services are currently offline, including the update download site: https://mastodon.social/@murena/113272432488332874 Background: Builds that start with IMG are fastboot images that cannot be imported as local updates in the updater app: > IMG-e-2.2-t-20240715417772-stable-FP5.zip is a fastboot package. It doesn't support installing via updater app. Download e-2.2-t-20240715417772-stable-FP5.zip then try sideloading. – https://gitlab.e.foundation/e/backlog/-/issues/8160#note_576544

Is there any way to make the built-in/factory-installed file manager on a Fairphone 3 remember the last target location I chose when I marked one or multiple files with a longer finger press and chose "move to"? I guess it's called "move to", my Android is not in English. I'm using Android 13.

I recently had to factory reset my phone due to it crashing to the Android Recovery screen. It seems that several other users have had the same issue; all in the past week. Is it possible to view system logs which were recorded prior to a factory reset, after the reset, in order to diagnose what may have caused this? I suspect it's not as the reset wipes data; but hoping that logs are put to one side somewhere before the reset so that infromation about the root cause can be identified after the device's issues are resolved & it's again accessible. Related: [FairPhone Forum discussion](https://forum.fairphone.com/t/stock-fp3-factory-reset-loop/90386/7) on the underlying issue.

On both Android phones I own (all systems up-to-date), MS Teams calls are not usable, since the caller voices are all squeaky. I have the impression that a compression algorithm in the background is not doing its job properly. The phones are a Fairphone 4 (with the latest eOS) and a Fairphone 3 (with the latest iodéOS). The problem occurs every time someone calls, both with and without video. Everything else seems to be working fine, just voice is unusable. Some internet searches reveal that the issue might not be related to MS Teams itself, but I doubt that, since normal calls and VOIP works just fine. So the question is: is there a workaround, some package that I’m missing, or is MS Teams plainly incompatible with de-Google-d operating systems?

I have a 1 TB SD Card in a Fairphone 3 running the latest Lineage. Recently I had issues with random reboots and now found out that my SD Card is formatted with FAT32, which might cause troubles on such a disk size. I tested a bit, and unlike lots of info on the internet, both exFAT and ext4 seem to be recognised just fine. And there is also F2FS which is touted as a good choice. So, which FS should I use? I use Linux everywhere so desktop OS compatibility is not a problem.

I’ve made a little mistake. This year, I’ve installed LineageOS for MicroG on my Fairphone3. It provides OTA updates but with the last one, it is said I must follow the official instructions on LineageOS website. It was not a prioritiy, so I didn’t do it. At the begining of the month, I’ve open the web page and read the instructions. There are simple, so i’ve done it. But, I’ve forgotten that my version was MicroG. I’ve installed the “normal” version (lineage-19.1-20220926). Now, my FP3 is in a bootloop . May be due to the absence of MicroG). I’ve tried to install a newer version of LineageOS for MicroG, without success. My problems are : - I would like to retrieve data - Data directory is encrypted - I’ve locked my phone with a pattern I’ve found a solution to try a decrypt with Santoku Linux. The script needs a header and a footer. I have found the header but not the footer. **Do you know where to find it ?** It seems these files are different accordind to the manufacturer.

This is my third attempt to install LineageOS (I've tried already with two other apparently supported devices, to no avail). I'm close to giving up. So I'll try to be as clear as possible. - I'm very comfortable using the Linux command line (I use it every day at work). My laptop has Fedora installed on it. - I have no "technical" experience with Android. My only experience is just using it as any other "non-technical" user would do. - I have a brand new Fairphone 3+ to which I want to install the latest LineageOS. The Fairphone 3+ is listed in the official list of supported devices. I followed the instructions mentioned here . I enabled USB debugging and unlocked the bootloader successfully. Then I went ahead and tried to flash the latest Lineage Recovery image (got it from here ), when I encountered the first problem: $ sudo platform-tools/fastboot flash boot lineage-18.1-20211213-recovery-FP3.img fastboot: error: boot partition is smaller than boot image The first option that came to my mind was to use TWRP because I know the image size of TWRP is smaller, but then I saw the warning at the end of this page that says that "Fairphone does not support the use of the TWRP". So I abandoned the idea of using TWRP. Then I read here that I should try to flash to boot_a or boot_b instead (no idea what that means). So I did: $ sudo platform-tools/fastboot flash boot_a lineage-18.1-20211213-recovery-FP3.img Sending 'boot_a' (65536 KB) OKAY [ 2.194s] Writing 'boot_a' OKAY [ 0.629s] Finished. Total time: 2.953s After that I went ahead and booted into recovery. I was surprised that it worked, but it did and I saw the Lineage Recovery menu. I did the mentioned factory reset successfully. But I got a problem during sideload: $ sudo platform-tools/adb sideload lineage-18.1-20211213-nightly-FP3-signed.zip adb: failed to read command: Success I noticed at the bottom of the phone's screen the following text: Now send the package you want to apply to the device with "adb sideload "... But when I executed the actual adb sideload ... command no text was appended to the phone's screen. Many sites mention that if the sideload stops at 47% and shows the failed to read command: Success message it means that it was in fact successful. But in my case there is no percentage at all. It seems as if the transfer doesn't even take place. Anyway, if a boot the phone normally I still boot into the "original" (or "factory") Android, not into LineageOS. So clearly the sideloading is not successful. What am I doing wrong? Is this problem maybe related to the first one (that the Lineage Recovery image was too big for the boot partition)? I'm slowly getting the feeling that the world of Android hacking (in the sense of just playing around) in general and of LineageOS in particular is just impenetrable and made just for a very few lucky geniuses.

Basically through the fastboot "API" i cannot access/see the Fairphone 3+, while theandroid debug bridge is working. Using adb devices lets me see the device and adb reboot bootloader reboots the phone. My steps so far are: **On Arch linux:** - installed: android-tools; android-udev and android-file-transfer - setup new udev rules for the device following this article. - SUBSYSTEM=="usb",ATTR{idVendor}=="...", MODE="0660", GROUP="adbusers", OWNER="..." - SUBSYSTEM=="usb",ATTR{idVendor}=="...",ATTR{idProduct}=="...",SYMLINK+="android_adb", OWNER="..." - SUBSYSTEM=="usb",ATTR{idVendor}=="...",ATTR{idProduct}=="...",SYMLINK+="android_fastboot", OWNER="..." - tried running fastboot as root **On Fairphone**: - enabled Developer mode - Get the IMEI and SerialNumber to unlock the bootloader code - Enable OEM unlocking - when fastbooting (through adb) - i select START and continue with the boot process ** Connection attempts** - Trying both USB 2.0 and USB 3.0 ports on my laptop - (The USB-C cable i am using is an official fp cable) When now using fastboot oem unlock or any fastboot command i get stuck with `` Maybe fastboot cannot access the USb devices? What do i have to do to actually be able to use fastboot?

As I understand it, if an Android device’s bootloader is locked (fastboot oem lock), it should check the installed system on boot to verify that it’s signed with some (the manufacturer’s?) signing keys. I’ve seen several warnings not to lock the bootloader again after installing a custom ROM like LineageOS because the bootloader would complain about the modified system image and refuse to boot. However, I have two Android devices on which I have installed custom ROMs: - The Fairphone 3 (FP3), where I installed /e/ OS - The OnePlus One (bacon) , where I installed LineageOS 18.1 (with microG) I’ve subsequently re-locked the bootloader on both devices and, surprisingly, not experienced any issues so far. For the Fairphone 3, I originally assumed that this works because /e/ OS is officially supported by the manufacturer, so I thought that the /e/ OS images are probably signed with some official keys. However, I don’t think there is any such support in the case of the OnePlus One (which is also long out of manufacturer support by now). Another hint is this forum post on the Fairphone forums , which reports the following: > I relocked the bootloader (fastboot flashing lock), it automatically > wiped my user data, and booted successfully! Also, after restoring my > data, I was able to upgrade from last-week’s release to the new > release of today - all without problems. > > Now, this does raise a lot of security questions though. I did not > realize that LineageOS, /e/ and even Fairphone where all signing their > builds with google test keys - essentially rendering the OS build > integrity checks meaningless… I guess in fact that means that it > doesnt really matter which keys are being used, as they are simply not > checked? Any key would be accepted? So, my question is: Why does running /e/ OS or LineageOS with a locked bootloader work in these cases? What is the significance of the Google test keys here – do the bootloaders just always accept them?

it seems I had a bad idea yesterday. I got a new SD card for my Fairphone 3+ (running Fairphone OS/Android 10). There was already an SD card inserted I assumed not to be in use. So I turned off the phone, exchanged the cards, booted the device and when asked to extend the phones memory I confirmed that. Now I have two problems: - I'm missing a couple of pictures. I wondered if these were on the old (luckily only 8GB) SD card and recognized that there are two partitions on it: android_meta and android_expand. As far as I learned, this means the SD card also was used as phone memory extension and thus encrypted. And the posts on Android Enthusiasts read like the phone has only one encryption key and won't recognize the old SD card anymore. - The Camera can't save pictures anymore. Whenever I take a photo I'm able to immediately open it by tapping its preview. Then I see a black picture, I'm told its size is 0 bytes and it's located in /storage/emulated/0/DCIM/Camera. Using the cx File Explorer I'm able to open that directory, but it's empty. And I'm not able to create files there. Using the ADB shell I was able to ls -la /storage the directory and got this:

sh
   total 7
   drwxr-xr-x  4 root root        80 2020-12-21 06:52 .
   drwxr-xr-x 21 root root      4096 2009-01-01 01:00 ..
   drwx--x--x  4 root sdcard_rw 3488 2021-01-12 21:38 emulated
   drwxr-xr-x  2 root root        60 1970-01-01 01:00 self

So only root is able to write in /storage/emulated. BTW: "total 7"? Currently I'm trying to find out the following: - is it possible to decrypt the pictures on the old SD card? Would be fine for me if it meant some work :) - is the encryption key for the old SD card still on the phone or could I reset the phone without making things worse regarding the old encrypted SD card? - is the phone in a bad state? - The Camera doesn't save pictures. - All other apps seem to work as expected. - The SD card overview in the Memory settings tell me there are apps on the new SD card (about 5GB). But when I tap the App category to get all apps listed, the list is empty. - When I eject the SD card, a couple of apps start, but only show a blank canvas. - if the phone is in a bad state: could this easily be fixed? If yes, how? Would be great to get some hints. Thank you very much in advance.

I’m trying to add the [F-Droid Privileged Extension](https://gitlab.com/fdroid/privileged-extension) using the OTA .zip to a [Fairphone 3](https://en.wikipedia.org/wiki/Fairphone_3) on which I’ve [installed /e/ OS](https://doc.e.foundation/devices/FP3/) . I tried modifying the update-binary script because the [mount points assumed in the script don’t quite seem to work on this device](https://gitlab.com/fdroid/privileged-extension/-/issues/69) , but although the files seem to be copied fine to the system partition(s) in recovery mode, when I reboot the phone, all the changes have disappeared. Is there anything else I need to do so that files copied to /dev/block/by-name/system_a or /dev/block/by-name/system_b in recovery mode stay around?

I'm used to the LED indicator light on the front for unseen notifications from Moto G2014/LineageOS 14. I searched for 10 minutes for a setting and I think I revisited all of them. There is however a LED in the front which indicates the charging progress. I assume it can be used for notifications as well. There're a few forum post which claim to explain how to enable it, but don't. The Fairphone has Android 9, updated yesterday.