Hi everyone,
I want to share my experience installing /e/OS 3.7.3 (Android 15) on a Fairphone 6 that came with Android 16 (build FP6.QREL.16.69.0, security patch May 5, 2026). It was a bit with some difficulties, but I finally succeeded. This post is not only about the technical steps – it also shows how an AI assistant (the one I was talking to) gave contradictory, wrong, and sometimes dangerous advice. Hopefully this helps others avoid the same traps.
Very quick summary of what I did before the big problems
These steps were fine – no issues here:
-
Prepared the Ubuntu computer
-
sudo apt install android-sdk-platform-tools -
Verified
adbandfastbootwork.
-
-
Unlocked the bootloader
-
Enabled OEM unlocking and USB debugging in developer options.
-
adb reboot bootloader→fastboot flashing unlock→ confirmed on phone. -
Everything was erased – expected.
-
-
Downloaded and verified the ROM
-
IMG-e-3.7.3-a15-20260506618655-official-FP6.zip -
Checked MD5 and SHA256 sums (they matched official values).
-
-
Tried to flash
/e/OScd ~/Descargas/eos_fp6→sudo ./flash_FP6_factory.sh
And here is where the nightmare began.
What went wrong (and what I learned)
-
Web installer is a trap – It always gets stuck at step 22/92% on FP6…
-
The assistant gave me wrong info – First said the /e/OS security patch was older (May 1) vs mine (May 5). Later said it was the same month. Real difference was small but not the cause of brick.
-
I almost believed my phone was bricked – Some suggested paying 50€ to Fairphone support. But my phone was detected in fastboot,
Device unlocked: true,get_unlock_ability: 1. That means it’s NOT bricked. -
Bootloop after flashing – The phone kept rebooting between Fairphone logo and bootloader warning.
-
No access to Recovery Mode – Selecting “Recovery mode” from fastboot just returned to the same menu.
What finally worked (manual method – no web installer)
I used a good USB data cable (not a charging‑only cable) and a USB 2.0 port on my computer. I did the normal installation These are the steps that saved my phone:
1. Check device state
bash
fastboot devices
fastboot oem device-info
fastboot flashing get_unlock_ability
2. Change active slot (this fixed the bootloop!)
bash
fastboot set_active other
fastboot reboot
If it still doesn’t boot, continue with manual flashing.
3. Flash essential partitions (assuming slot a is active – adjust letter if needed)
bash
fastboot flash boot_a boot.img
fastboot flash vendor_boot_a vendor_boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_system_a vbmeta_system.img
fastboot flash super super.img
fastboot flash init_boot_a init_boot.img # if present
fastboot flash recovery_a recovery.img
4. Wipe user data
bash
fastboot erase userdata
fastboot erase metadata
5. Reboot
bash
fastboot reboot
After first boot – important steps
-
Insert your SIM before the first boot (or immediately after, then reboot). This helps the system configure APNs automatically.
-
Go to Settings → System → App Compatibility (“microG Settings” ).
Enable Google Device Registration and Cloud Messaging.
Bootloader – DO NOT LOCK IT
I left the bootloader unlocked. The warning message at startup is harmless and doesn’t affect daily use. Locking it with a ROM that has an older security patch could cause a real brick.
Tools that helped
-
fastbootcommands – manual flashing is more reliable than the web installer. -
A spare USB cable and trying different ports solved many “stuck” errors.
-
sudo killall fastboot adbbefore retrying a failed flash.
Final thoughts
I’m now running /e/OS on my Fairphone 6 with ZERO Google! and everything works!! If you’re stuck in a bootloop, don’t panic – first try changing the active slot. Don’t trust any assistant that says your phone is bricked without running fastboot oem device-info. And please avoid the web installer on FP6.
I hope this helps someone. Thank you for your attention and remember to help Free Palestine, support Resistance, support Justice