The upgrade documents are not correct. We are working on improving the install and upgrade guides. Disabling the upgrade guide for the FP3 while this is rework is in progress
2 Likes
The docs still mention /e/ Recovery, but the download page only provides an install image, and no recovery image… I guess something is broken here.
2 Likes
The FP3 install file includes the recovery file. Follow the steps in the guide to install the recovery as part of the process. No need to separately download and install it. The reference to the recovery needs to be removed from the guide.
3 Likes
Bonjour,
Mon fp3+ ,avec la version 1.1 marche très bien ,pour ce que j’ai testé, à savoir applounge qui ne plante plus et camera. Je vous toens au courant plus tard pour le reste.
Une suggestion: un raccourci sur le bureau vers le cloud et la communauté. Mais peut être que c’est déjà possible et que je n’ai pas compris comment faire.
Autre suggestion: que l’on puosse créer dds dossiers d’appli sur bliss.
Merci pour votre super boulot. Bel été à tous.
1 Like
@Manoj the installer guide is completely useless at the moment. The only zip file I could find to download is the official system.zip : https://images.ecloud.global/dev/FP3
then the guide asks me to
- Unzip the archive
- Confirm that extracted directory contains following content:
bin-linux-x86 directory- which contains linux tools including fastboot and adbbin-msys directory- which contains Windows tools including fastboot and adbimg files- Theimgfiles that are to be flashed onto the device.flash_FP3_factory.sh- The installer script.
but it DOESN’T. it just contains the img files, nothing else.
is it really me??
2 Likes
Same problem with IMG-e-1.1-r-…
Does anybody found a work-around?
In the guide for FP4 there are commands like
fastboot flash bluetooth_a bluetooth.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash devcfg_a devcfg.img
fastboot flash devcfg_b devcfg.img
…
That could be adjusted to the img files present in the FP3 zip.
Isnt that what the flash script does anyway?
Thanks in advance!
(Sorry for insisting, but older stable release is no option for me.)
1 Like
The FP3 releases themselves are fine up to now, content-wise nothing changed compared to prior releases, it was always just image files.
It’s the install guide that’s broken currently.
@Manoj: Is there a timeline for the fixing of the install guide? Or will future releases match the current install guide?
In the meantime, Wayback Machine to the rescue …
https://web.archive.org/web/20220413173954/https://doc.e.foundation/devices/FP3/install
1 Like
ok, this is bad. It was supposed to be added to the v1.4 build and seems to have missed. Have passed on to the build team to resolve. Will update.
2 Likes
We will push a v1.4.1 specifically for the FP3 with the correct set of files, hopefully by early next week.
2 Likes
Hello, the title won’t be ‘’ Fairphone FP3 - FP3+’’?
1 Like
changed as required
3 Likes
Hi Manoj, can you estimate, when the 1.4.1 will come?
1 Like
I have not got an update as yet on this. Will check again on Monday and get back
1 Like
The 1.4 Version (e_FP3-userdebug 11 RQ3A.211001.001 eng.root.20220922.215721 dev-keys) works fine on my FP3
The correct folder structure should be visible on the stable and dev builds now.
The one build on which it is still pending is the FP3 Q dev build. Will try to get it out as part of the v1.4 or the next v1.5 which should be released in the week after next.
1 Like
https://doc.e.foundation/devices/FP3/upgrade
Warning: Please note this upgrade build could not be tested as there were no device specific testers available. Some devices may need a revert to stock ROM prior to upgrade. To flash the stock ROM you would need to use a tool provided by your vendor. You may also need to download a recovery image built specifically for your device.****
Is this really true for FP3?
And also, in this guide it says sideloading work but that is not the case when you have a locked bootloader
The flash instructions are outdated as for the S dev (or other dev) builds.
The complete section “Installing /e/OS from the bootloader” refers to unzipping and starting “flash_FP3_factory.sh” but the latest dev builds contain the complete OTA which is just a payload.bin file.
So it needs to be flashed by sideloading and not via “flash_FP3_factory.sh”.