FP4 bricked upon 5.5 beta tester update

Hello Iodé,
The 5.5 beta update was installed yesterday night at 2300 AMS time.
After install, the system called for a reboot.
I started the reboot,
I got no error messages whatsoever.
Thereafter the system did not boot, Phone is stuck at a Faiphone screen, but does not get any further,

How can I revert to previous version. It’s a a brick now.

We’re currently investigating the issue, sorry for that broken beta build.
To revert to a previous version, you must install LineageOS recovery (iodé one does not permit to install a previous version), and sideload version 5.4.
Or, wait a couple of hours, maybe a new update will be proposed.

Where is the zip file for 5.4 again?

And would this recovery (version 21.0-20240911-nightly) work?

Yes for the recovery.

Thanks confirming receipt of the issue.
I appreciate that it may take some time on your side to solve the matter.

I attach two screens. One is the screen that I get after starting the phone. The other is the FP4 screen that is stalled. Usually the next screen is the Iodé start screen. That does not emerge.

At this state of brickiness I do not know how to follow up your recommendations. The phone won’t connect to my PC by any means (e.g. cable does not create a link). So adb is not available.

The previous beta version is still on the phone. However I do not know how to access it.

Any suggestions?


Well, I got mine to boot again after it switched itself to slot b (the 5.5 update was installed to slot a)

But if you’re going to go the route of using the lineage recovery and reflashing 5.4, you need to use fastboot commands after booting to the bootloader

A fixed beta build is available here: iode-5.5-20240913-FP4-ota.zip · master · ota / betas · GitLab.
From the fastboot screen, you should be able to boot to recovery, and then sideload this build.

Hi Vince,

I might need some more detailed instructions.
I found the recovery

From the screen of your first picture: press volume up several times until you see “Recovery” in red, then press power. Once in the recovery, go to “Apply update”, then “Apply from ADB”. Start the sideload from computer: adb sideload iode-5.5-…

Inside Revovery, 2 possible actions:
ADB sideload
Cancel

And at the bottom of the screen: “Now send package you want to apply to the device with etc…”

Challenge: How to get the PC see the device? It is plugged in (cable). However, PC does not see it

Fairphone recommends these drivers for windows: https://adb.clockworkmod.com/

OK, Vince, still trying…
Please note the last time I used adb was when I put Iode on this FP4.
It feels like 100 years ago.
Greetz

Great! It’s running again.
Thanks for fast response

Greetz!

1 Like

You’re welcome. And sorry for the broken build… beta-testing may by a bit risky :wink:

I hope it gave you some useful feedback!

Hi,

I tried the way described above:
adb Sideload wasn´t possible.
So i flashed LineageOS recovery to downgrade to IodeOS 4.5: not working.

Tried to sideload iode-5.5-20240913-FP4-ota.zip (still LineageOS recovery):

ERROR: recovery: failed to verify whole-file signature
Update package verification took 75.5 s (result 1).
ERROR: recovery: Signature verification failed
ERROR: recovery: error: 21
Installing update…
Step 1/2
Error applying update: 7 (ErrorCode: :kInstallDeviceOpenError)
ERROR: recovery: Error in /sideload/package.zip (status 1)

Install completed witch status 1.
Installation aborted

Hi there,
I had this issue when sideloading. I tried with this version iode-5.5-20240913-FP4-ota.zip · master · ota / betas · GitLab
When I try to reboot, it’s always stuck on the Fairphone logo.

Note: I’m on Ubuntu 24.04 and did sudo apt install adb fastboot in order to get adb and fastboot working

I just tried again twice, and it always crashes at 47% of the sideload on my Ubuntu terminal.
Here’s a picture of what’s on my FP4:

same picture here. :person_shrugging:

using windows platform-tools

Hi @f.limi,
You mentioned earlier that you also had some signature errors, if I don’t mistake. Do these showed when you tried to downgrade, or also when you tried to install iode-5.5… ?