The workaround for the occuring problem: couldn’t parse partition size ‘0x’ Did only work partly. The thing that finally worked was to use the command: Fastboot flash boot_a boot.img
Without the previous commands, so in total:
The version of fastboot that came with debian buster and ubuntu bionic is broken. If you keep getting mke2fs errors, this is a known problem in that version but they included it in their release anyway, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924591
I worked around this by doing the install from xenial, which worked perfectly.
The solution is to use the current Android SDK platform tools directly from Google anyway.
Section “Requirements” step 2 of the install guide includes a link to a setup guide to achieve this … https://wiki.lineageos.org/adb_fastboot_guide.html.
An additional hint was added to advise users to really follow this setup guide to avoid “unexpected issues”.
Another option, but is that easy enough? Installing from the package manager tends to be the easiest approach…
But I don’t understand why the distributors still provide a packaged fastboot if for whatever reason they can’t make it work (from what I gather in the link above, it seems fixing fastboot would break other parts of their system so they chose not to).
(sorry for the duplicate, I’m still learning how this works…)
Hey, I am new to e/OS and the last custom ROM that I flashed is atleast 5 years ago, so I am quite deppendend on the guide.
For unlocking the bootloader, after you already are in the bootloader, I have to finally unlock it with the command
fastboot flashing unlock
this worked for me, but the step afterwards
The device reboot automatically. It will show a warning. Press Volume + or Volume - to display boot options, select fastboot and confirm with Power to reboot on fastboot
Wasn’t the same for me. I only could interupt the reboot with Volume + or Volume - nothing else.
Did something changed recently?
Now when I boot into the bootloader again it says that fastboot is enabled and the device is unlocked.
I can select:
Recovery Mode
Start
Restart bootloader
Power off
Nothing with fastboot. I highly suspect that Recovery Mode is the way to go for the next step.
While fastboot -w in the bootloader gave me a waiting for device or something similar.
Edit: now I tried again fastboot -w on the bootloader to see the exact message and it erased my user data this time, without changing anything. is this the right way or did I fucked up?
In Failed update, why (q0.17, FP3) the original poster said something about TWRP being mentioned in the install instructions.
After having a look I indeed found
TWRP
Errors while running TWRP version 3.4.x.x or above - Try downloading and using a previous TWRP version… below 3.4.x.x
In TWRP if this error shows up failed to mount /preload - Try in TWRP wipe screen in advanced menu select preload and swipe to wipe
/cache/recovery/xxx -> no such file or directory error while flashing a ROM - On PC run adb shell in the console now create a folder called recovery for e.g. here the devicecode name is violet “violet :/cache# mkdir recovery”
in an expandable section called “To find some troubleshooting tips… click here”.
I assume that’s part of a template included in all/most docs?
Not sure if it applies to the FP3.
I have a Fairphone 3+ with pre-installed /e/ OS. I received messages that updates are available for 0.21 (22.01.22) and 0.22 (28.02.2022). I understand that these must be installed manually, but cannot work with the information provided on the page referred to above.
In particular, I cannot relate the /e/OS reference displayed on my phones´ “Systemupdates” (0.21-2022012215…) with the exact build to be downloaded.
Also, I cannot separate descriptions for Windows and Linux users.
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
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.
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.
@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 adb
bin-msys directory - which contains Windows tools including fastboot and adb
img files - The img files 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.
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.)
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?