FP 5 - Upgrade/Install went wrong (now: stuck in bootloader) - iode

[Tooli]

Hi - i almost cry right now.

I was manually upgrading from Iode 6.9 to 7 while using the manual ( ota / ota · GitLab ) “How to flash Fairphone”, after running flash-all.sh on my linux system the device says „Your device is corrupt. It can’t be trusted and may not work properly“. After that it loop all the time back to the bootloader screen.

• Restart bootloader

• Recovery mode

• Start

… always bring the device back to bootloader mode within 1 or 2 seconds.

ADB don’t recognise any device even afters removing the battery and put it back in.

The Iode-Installer 0.3 even gave an error “unsupported device”

While connecting to my computer it says “Google Andoid is connected” instead of “Fairphone5. Thats weird…

Even on https://flash.android.com/ i got an connection error

Is there any chance to install iode or bring stock back - or do i have to throw my fairphone 5 out of my window?

[piero-e]

Hello @Tooli,Welcome to the Fairphone users forum.

hopefully, the bootloader looks still unlocked
please confirm by running

fastboot oem device-info

also you could try booting on the other slot

fastboot set_active other

even thinked for another alternative android OS, you can take inspiration reading
A clear guide to install /e/OS on your Fairphone

[Tooli]

Hi Piero, thanks for your reply

Indeed i do confirm, that something went different.

I did both:

$ sudo fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
OKAY [ 0.000s]
Finished. Total time: 0.000s

$ sudo fastboot set_active other
< waiting for any device >
Setting current slot to ‘a’ OKAY [ 0.028s]
Finished. Total time: 0.032s

After that my FP got in a bootloop (seems the system is broken) not able to do anything.

When i poweroff and poweron it again, the same thing happens what i’ve explained (Bootloader without any escape).

[piero-e]

ok, what if you run the install script again ?

[Tooli]

While idleing in bootloader nothing:

$./flash-all.sh
Erasing 'avb_custom_key' OKAY [ 0.007s]
Finished. Total time: 0.009s
Warning: skip copying avb_custom_key image avb footer (avb_custom_key partition size: 0, avb_custom_key image size: 1032).
Sending 'avb_custom_key' (1 KB)

It’ stuck there.

Edit: I try using fastboot update <iode-7.1-20251225-FP5-img.zip>

It seems like an normal update, but failed again (for a second i saw the lineage recovery symbol on screen) and did a bootloop:

$ sudo fastboot update iode-7.1-20251225-FP5-img.zip
< waiting for any device >

Bootloader Version…: FP5.VT2D.C.054.20250814
Baseband Version…: 13
Serial Number…: ———-

extracting android-info.txt (0 MB) to RAM…
Checking ‘product’ OKAY [ 0.002s]
Setting current slot to ‘a’ OKAY [ 0.007s]
extracting fastboot-info.txt (0 MB) to RAM…
extracting super_empty.img (0 MB) to RAM…
extracting super_empty.img (0 MB) to disk… took 0.000s
Writable partitions are not supported
extracting super_empty.img (0 MB) to RAM…
extracting super_empty.img (0 MB) to RAM…
extracting super_empty.img (0 MB) to RAM…
extracting super_empty.img (0 MB) to RAM…
extracting super_empty.img (0 MB) to RAM…
extracting super_empty.img (0 MB) to RAM…
extracting super_empty.img (0 MB) to RAM…
extracting super_empty.img (0 MB) to RAM…
extracting super_empty.img (0 MB) to RAM…
extracting super_empty.img (0 MB) to RAM…
extracting super_empty.img (0 MB) to RAM…
extracting super_empty.img (0 MB) to RAM…
extracting boot.img (96 MB) to disk… took 0.237s
archive does not contain ‘boot.sig’
extracting super_empty.img (0 MB) to RAM…
Sending ‘boot_a’ (98304 KB) OKAY [ 2.397s]
Writing ‘boot_a’ OKAY [ 0.235s]
extracting super_empty.img (0 MB) to RAM…
extracting dtbo.img (24 MB) to disk… took 0.048s
archive does not contain ‘dtbo.sig’
extracting super_empty.img (0 MB) to RAM…
Sending ‘dtbo’ (24576 KB) OKAY [ 0.594s]
Writing ‘dtbo’ OKAY [ 0.058s]
extracting super_empty.img (0 MB) to RAM…
extracting vendor_boot.img (96 MB) to disk… took 0.194s
archive does not contain ‘vendor_boot.sig’
extracting super_empty.img (0 MB) to RAM…
Sending ‘vendor_boot’ (98304 KB) OKAY [ 2.387s]
Writing ‘vendor_boot’ OKAY [ 0.213s]
extracting super_empty.img (0 MB) to RAM…
extracting vbmeta.img (0 MB) to disk… took 0.000s
archive does not contain ‘vbmeta.sig’
extracting super_empty.img (0 MB) to RAM…
Sending ‘vbmeta’ (8 KB) OKAY [ 0.001s]
Writing ‘vbmeta’ OKAY [ 0.001s]
extracting super_empty.img (0 MB) to RAM…
extracting vbmeta_system.img (0 MB) to disk… took 0.000s
archive does not contain ‘vbmeta_system.sig’
extracting super_empty.img (0 MB) to RAM…
Sending ‘vbmeta_system’ (4 KB) OKAY [ 0.001s]
Writing ‘vbmeta_system’ OKAY [ 0.001s]
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.

[piero-e]

@Tooli

< waiting for any device >

try another cable, and / or another USB port.

[Tooli]

Hi Piero - thanks for your support (more mental)

I did it - installing lineage in following steps:

fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img
adb -d sideload /path/to/zip

I had to reboot the bootloader a couple times, but finally have a working lineageOS

Now i will try to install Iode via Iode-Installer Tool.

Edit: Install via Iode-Installer Tool isn’t working (device isn’t supported)