[LEGACY_BUILDS] /e/-OS-R for the Fairphone 2 (FP2)

as developpement on some devices has been dropped on version e-2.2-r
the /e/ management decided to qualify those dropped devices as “legacy devices”.
But since the latest builds released by the /e/foundation for “legacy devices” are currently unavailables,
i wanted to make builds for devices where UNOFFICIAL builds don’t already exist or are outdated…

.

this LEGACY version is not an Update !

it is builded from the exact same source code as “e-2.2-r-20240719418592-dev-FP2.zip”
but i don’t own this device myself, so :

please have a test and share feedback !

because others users need to how it’s works…

.

instructions and downloads : ( :warning:…work in progress…:warning: )

.

by install-script for full installation on new devices (you will loose your data)
instructions for install-script

.

by the traditionnal way for familiar users, or update, upgrade (preserve your data)

.

.

.

install a recovery manager

:warning: work in progress… :warning:

Fastboot Install Method (No Root Required):


You will need the platform-tools from the Android SDK on your computer. Download the platform-tools as per your operating system.

Windows users will need proper drivers installed on their computer. You can try the simple FWUL adb/fastboot ISO or the Naked ADB drivers or the Universal ADB drivers if you don’t already have a working driver installed

On your device, go into Settings → About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging. From your computer, open a command prompt and type:

adb reboot bootloader

You should now be in fastboot mode.

Download the correct image file and copy the file into the same folder as your platform-tools. Rename the image to twrp.img and type:

fastboot flash recovery recoveryname.img
fastboot reboot

immediatelly after typing fastboot reboot, hold the key combo,
Volume Up + Power to be sure to reboot to the custom recovery.
Once it is booted, the custom recovery will patch the stock ROM to prevent the stock ROM from keping its own recovery.
If you don’t follow this step, you will have to repeat the install.

.

Now the easiest part : install /e/ !

*. tap back to the main menu


.

  • choose Advanced


.

.

  • Tap ADB Sideload

image
.

  • Select Wipe Dalvik Cache and Wipe Cache

  • then Swipe to Start ADB Sideload


.

on your PC

  • in the command-prompt on your Windows PC,
    or in the console on your MacOS PC
    In the Terminal application on your GNU/Linux PC,
    navigate to file path where you have downloaded the /e/OS.zip to execute the following command:

adb sideload e-0.11-n-2020082970471-dev-your-device.zip

  • It will result in the following output on PC when finished:

serving: '/home/modi/Downloads/e-0.11-n-2020082970471-dev-herolte.zip' (~47%) Total xfer: 1.00x

  • On your smartphone, a successful result as seen in the image below appears.
    .

    .
  • Tap Reboot System


  • wait several minutes…

to boot into freshly installed /e/OS on your Samsung device.


.

  • Voila! Easy, isn’t it?

If you encounter an “error 7”,


.
refer to this topic .
This could also be due to the fact that :
your TWRP version isn’t compatible with the ROM you are trying to install,

      • Samsung.
        for installing /e/OS on a recent devices “a/b_slot” or “treble” ( originaly shipped with Android 8 or later ) use twrp version 3.5.x-x
        twrp version 3.4.x-x was buggy, don’t choose it
        BUT for installing /e/OS on an older device ( originaly shipped with nougat.7, or older), better is to use a version like twrp 3.3.1-0

[/details]
.

using recovery-e

The e-recovery.img will perform many of the same functions as twrp and is probably a bit easier in some respects for installing the eOS.zip. There are just a few basic steps to carry out:

  • (only for new install, not for update), select Factory Reset, then Format data / factory reset and continue with the formatting process
  • Return to Home Screen
  • Select Apply Update, then Apply from ADB

Now turn to your computer and issue the command to sideload the eOS installation zip

adb sideload filename.zip

When installation has finished, return to the main menu, tap Reboot system now

Your phone should now boot into eOS.

Step-by-step, with images

The e-recovery Home Screen. Select Factory reset

Select Format data/factory reset (notice the output appearing at the bottom of the screen)

Then press the arrow at the top of the screen to return to Home Screen

Select Apply Update, then Apply from ADB

The screen should now change and the output at the bottom ask you to send the package from your computer.

On the computer issue command to sideload the eOS installation zip.

adb sideload e-1.18-t-for-your-device.zip

the phone screen will be mostly blank with just the output at the bottom showing progress.

On the computer the sideloading shows progress as a percentage figure that will stop at 47%. The phone will still be installing though (even though it might feel like nothing is happening sometimes!) and you can expect to see the following screens

Then press the arrow at the top of the screen to return to Home Screen

Tap Reboot system now to boot into eOS.

.

Thanks for reading !
Share your feedback.

.

9) Install the image of /e/OS on the ROM of your device without computer, from the “custom recovery manager” using the SDcard or internal storage method

(forked from @Anonyme)

Now you’re in TWRP, congratulations, you’ve done the hardest part.

using TWRP

.

A) Delete existing smartphone content

  1. Before you reach the main menu, a message may ask you if you want to open TWRP read-only (i.e. no risk of deleting or changing anything) or not. This option shouldn’t be chosen (since we want to install a new operating system). Slide the bottom arrow from left to right.TWRP may also ask you for a password, which is your phone password.

  2. a)


.

  • Tap Wipe from Main Menu.
    image
    .

  • Ta.p Format Data (only for new install, not for Update)


    .

  • Type yes in the text field to continue.


.

  • Once done a successful result as seen in the image below appears.

This will remove encryption as well as delete all files stored on the internal storage.

  • T.ap Back, return to the main menu, choose reboot ,

image

  • image

the device reboot to TWRP

  1. b)


.
and tap Advanced Wipe .

  1. Select the following items to delete and nothing else :
  • Dalvik / ART Cache
  • system
  • Data (only for new install, not for Update)
  • Internal Storage (only for new install, not for Update)
  • cache


.
4. Validate by dragging the “Swipe to Wipe” arrow from left to right.

If red error messages show up, your phone is probably encypted but TWRP can’t decrypt the /data partition (it’s a common issue on Samsung phones).To solve that problem, go to Wipe > Advanced wipe, select “data”, click on “Repair or Change File System”, then on “Change filesystem”. Select exFAT (or another one if it doesn’t work, it doesn’t matter), then swipe from the left to the right. Redo the manipulation but this time select ext4 (which is the original file system) then slide from the left to the right.
Go to the 8)A)1. part of the howto.

  1. Return to the main menu using the virtual buttons at the bottom of the screen.

B) Transfer the /e/ ROM to the internal storage of the smartphone

The previously downloaded /e/ ROM is waiting in the warm on your computer, so you need to transfer it to your smartphone’s internal storage so that TWRP can use it.

  1. Connect your smartphone to the computer.
  2. Copy the ZIP file of the /e/ build (without unzipping) (right click on it and then “Copy”).


.
3. Paste it into the internal storage of your smartphone. To do this, in the file explorer you are in, clic.k on “This PC” then on your smartphone, then on “Internal storage”. Paste here, next to the “TWRP” folder (not inside).

  1. Unplug your smartphone once the transfer is complete.

C) Install /e/

Everything is ready, all that remains is to install /e/.

  1. In the TWRP main menu, click on “Install”.


.
2. Select the .zip file you just copied/pasted. It should appear directly if you have pasted it at the right place.


.
3. To confirm the flash of your smartphone, slide the “Swipe to confirm Flash” arrow from left to right.

  1. A blue loading bar or a shiny empty bar should appear. After a few minutes at most, the installation is completed.

If you encounter an “error 7”, refer to this topic .
This could also be due to the fact that :

  • your TWRP version isn’t compatible with the ROM you are trying to install,
  1. Click on “Wipe cache/dalvik” at the bottom left, confirm if necessary.


.
6. Click on “Reboot System”. You can choose whether or not to install the TWRP application on /e/ and choose whether or not you want this application to be a system application. Since it’s not useful, I preferred to click on “Don’t install TWRP App” and DO NOT INSTALL drag the arrow from left to right (this. would have resulted in its installation).

.

using recovery-e

Copy the “e…your-device-codename.zip” into your sdcard

Boot your device into " recovery mode"
and peform a “Factory reset” (only for new install, not for update)

Then select “Apply Update”

Then select “Apply Update”

Choose from internal storage
or
Choose from sdcard1

Select the folder where you put the downloaded file
Choose from sdcard1

Select the folder where you put the downloaded file

Choose the last /e/build
Choose the last /e/build

wait severals minutes …

Go back to the main menu
Using the “<–” bouton at the top left of the screen

wait severals minutes …

Go back to the main menu
Using the “<–” bouton at the top left of the screen

Choose “Reboot the device now”, it’s done !

Choose “Reboot the device now”,

it’s done !

.

.

Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online servicesphone

4 Likes

I did follow these instructions but it was back in may 2024 and at that time I used the image here : https://images.ecloud.global/dev/FP2/ . It is working perfectly well. But I assume you are more interested in the community build.

hello @niels-FP2, welcome to this forum.

what i understand, is you installed /e/ on your FP2 in may 2024 with the currently unavailable files and you are happy with it.
i am also happy with my FP3 since 2 months it replace my loved s4mini, i was fedup with the baterry life (3 battery per day the last times) i loved it because it is small, easily repairable and cost 30€, the Fairphone is also esily repairable, that why i choose it, even it is much bigger and cost me 100€.

what i don’t understand is :

because i provide 2 differentes methods here…

also :

dev builds have been renamed community builds.
mines meets the UNOFFICIAL requirements (same code as dev / community builds simply builded by user not by /e/ 's computers)

as developpement on some devices has been dropped on version 2.2-r since 2024 july (last security patch was from 2024 fabruary) last version buildable is 2.3-r identical to 2.2-r, there will be no more possible version updates, for dev / community and UNOFFICIAL builds…
e-2.3-r-20280728-UNOFFICIAL will be the same as e-2.3-r-20240911-UNOFFICIAL
no more changes in the source code excepting to become CUSTOM builds…

the /e/ decided to qualify those dropped devices as “legacy devices”.
i liked to decide to call those builds as LEGACY BUILDS even if the present version is UNOFFICIAL in fact,

yes, I did install /e/ on my FP2 in may 2024 with the currently unavailable files. I don’t think I did use a script so I must have used the traditional method.

1 Like

Hello!
Thank you for your effort of keeping legacy builds available :slight_smile:

I downloaded the second option “traditional way”.
Installing the zip first with TWRP 3.5.2-9 (the one that was already installed as recovery on my FP2) resulted in a bootloop.
However after flashing your TWRP 3.7.0-9 the system is correctly booting :smiley: .

2 Likes

Hi @piero , I’m new here and I just got the FP2.

First of all, thanks for the effort of releasing this build !

Unfortunately for me, I tried the install script but I run into this error

error: cannot load '/*****/IMG-e-2.3-r-20250111-legacy-FP2/rpm.img': No such file or directory

ERROR: Could not flash the rpm partition on device 79d*****.

ERROR: Please unplug the phone, take the battery out, boot the device into
ERROR: fastboot mode, and start this script again.
ERROR: (To get to fastboot mode, press Volume-Down and plug in the USB)
ERROR: (cable until the fastboot menu appears.)

I did what was suggested by the script and tried again but it always crashes on this error… :cry:

Is there a way to get this rpm.img file ?
Or should I update the script to skip it ?

Current OS on the phone is Fairphone OS 19, maybe I should update it to version 23 first ??

I did install some TWRP on other phones in the past, but I’d prefer to use the CLI way. If it does not work, I’ll try the “traditional way” which seems to have worked for @oli.sax !
Cheers

2 Likes

Hi @oli.sax, welcome to this forum.

First thank you for testing Alpha-1 and sharing feedback,
as i am curious i’d like more details :

  1. what was the previous system version installed on your device ?
  2. Does new system “trust” feature claim about signed with public keys, as on my Galaxy s4 ?
    → i already have a new version for the FP2 that i hope could solve this issue with dev keys.

Also can you please publish a screenshot showing the legacy version number frim setting → about the phone → anndroid version 11–> …

[UPDATE] after upgrading to latest Fairphone OS (version 23 / Android 10) still no luck.

After reading the script, I can see that some of the .img files requested are not present in the Zip file

flash_image_or_abort "${sn}" rpm "${IMAGES_DIR}/rpm.img"
  flash_image_or_abort "${sn}" sbl1 "${IMAGES_DIR}/sbl1.img"
  flash_image_or_abort "${sn}" tz "${IMAGES_DIR}/tz.img"
  flash_image_or_abort "${sn}" modem "${IMAGES_DIR}/modem.img"
  flash_image_or_abort "${sn}" splash "${IMAGES_DIR}/splash.img"
  flash_image_or_abort "${sn}" aboot "${IMAGES_DIR}/aboot.img"
  flash_image_or_abort "${sn}" boot "${IMAGES_DIR}/boot.img"
  flash_image_or_abort "${sn}" recovery "${IMAGES_DIR}/recovery.img"
  flash_image_or_abort "${sn}" system "${IMAGES_DIR}/system.img"

  if [ "${CLEAN_FLASH}" = "true" ]
  then
    flash_image_or_abort "${sn}" userdata "${IMAGES_DIR}/userdata.img"
    flash_image_or_abort "${sn}" cache "${IMAGES_DIR}/cache.img"
  fi

in the file I only found these :

  • boot.img
  • cache.img
  • recovery.img
  • system.img
  • userdata.img

Would it be ok if I only flash those ?

Hi piero!
Previously installed was DivestOS.
After years of intense use my FP2 is quite unstable so nowadays I use it only for test.

I can also test the script install option, if needed.

No error message about self-signed keys.

Olivier

2 Likes

And here is the screenshot :slight_smile:

2 Likes

Hi @KOBe, welcome to this forum.

Second thank you for testing the Alpha-1 and sharing feedback,

it was not produced during the build, i will investigate if it expected
look like it is a firmware part, not system
the partition should already exist on your device,

I finally managed to get it installed via TWRP with the other method !
It seems very unstable (lots of UI crashes and lags) but it kinda works :slight_smile:
Fairphone 2 is probably too old as a phone now, I’ll see if I manage to get better results by fine tuning settings

Same for me… It took me 3 trials to get the screenshot above, because the settings were hanging or crashing :sweat_smile:

@oli.sax, @KOBe
sorry,
i have removed the faulty files…
and just uploaded the “alpha-2” builds, hopefully signed with dev-keys… hopefully working…
links have been updated.

1 Like

on my Galaxy s4 (jfltexx) gt-i9505 :

we see differents dates and release type in “e/ OS version”
also differents signatures keys in “Build number”

between RC-1 et RC-2

I had a look in the original file IMG-e-2.2-r-20240719418592-dev-FP2.zip (one friend downloaded it while it was still available) and the rpm partition is present in the build…

yes he send it to me, i already hosted it on the “/e-os-legacy-builds” server.
as i spent some hours and white nights learning building to acheive that e-2.3-r-legacy, i’d like you to test current available Alpha-2 build,

  • KOBe, a clean install from stock (i have a trick i mind in case)
  • oli.sax a dirty flash over DivestOS and/or an older /e/ version (could be e-2.2-r-dev if you don’t have older)

thank you for your support.

1 Like

hi @piero ,

I’ve been trying to download the image from SourceForge, but it’s tedious.
Download speed is 120Ko/s at max (probably due to server limitations) and so the download keeps failing after 1h or so (also probably due to server limitations).

I’ve been retrying all morning (3 or 4 times now) and it’s quite anoying :cry:

Would you mind putting those on Lufi so it would be easier to download, please ?

If not, I’ll just keep retrying

1 Like

The Internet Gods have been good to me, I finally managed to download the file :slight_smile:

1 Like

low performances could be due to the fact i was uploading at the same time, i don’t know how it works really, @ronnz has often same bad download speed by moments on his server for Unnoficial Upgrade or Unsupported Builds
the Lufi link was just ready when i saw you success.

1 Like