Fairphone 3 (FP3)

007fred50

@Luksus can't get it to work here is my steps:

cd Fairphone_FP3_FP3_9_8901.2.A.0111.20200131_01311418_user_release-keys/
fastboot flash system system.img
fastboot boot twrp-3.4.0-0-FP3.img
adb disable-verity
fastboot -w
fastboot reboot
fastboot flash boot halium-boot.img

I can't get thiss to work:

adb shell mount /system_root
adb push treble-overlay-fairphone-fp3.apk /system/overlay/

It stuck on boot up logo (Fairphone 3+ Logo)

Luksus

Please just save this script in the folder, where the unzipped images are.
Then boot the phone into fastboot mode.
Then execute this script sh flash.sh
If it succeeds, boot the phone into fastboot mode again.
Execute the script again.

Do not use twrp or flash any GSI, before you have a working android again.
Please refer to Fairphone Forum, if you have issues, to get a working android again.

007fred50

@Luksus but that will replease all files inside (Zip).

Can i go back to Farphone OS again? (Android 10)

Just to be sure.

install Fairphone OS / Android 9
Install GSI / follow that guide here https://forum.fairphone.com/t/how-to-flash-a-custom-rom-on-fp3-with-gsi/57074

007fred50

This post is deleted!

Luksus

@007fred50 said in Fairphone 3 (FP3):

@Luksus but that will replease all files inside (Zip).

Can i go back to Farphone OS again? (Android 10)

Yes. "Just" follow this guide: https://support.fairphone.com/hc/en-us/articles/360048050332

Just to be sure.

install Fairphone OS / Android 9

Yes

Install GSI / follow that guide here https://forum.fairphone.com/t/how-to-flash-a-custom-rom-on-fp3-with-gsi/57074

No. After you have a working Android 9 follow my guide:

Flash

Boot the phone into bootloader/fastboot by pressing power + volume-down buttons until it reboots. Or just reboot and click a volume button within 5 seconds and select the bootloader.
Flash halium-boot image: $ fastboot flash boot halium-boot.img
Boot your downloaded TWRP image temporarly: $ fastboot boot [twrp-image.img]
In TWRP, wipe data only
In TWRP go to ADVANCED and Select "ADB Sideload". Activate sideload.
in Terminal: $ adb sideload [ubports_gsi.zip]
Wait until it finished, then reboot system.

007fred50

@Luksus the link you gave me with Android 9..

it is android 10 (Fairphone_FP3_FP3_9_8901.2.A.0111.20200131_01311418_user_release-keys.zip)

Luksus

@007fred50 is it? ok, then just use the other zip 0110.

007fred50

@Luksus so many thing where can i download zip 0110?

Luksus

@007fred50 said in Fairphone 3 (FP3):

@Luksus there are no flash_stock.sh inside the file / Zip

wrong file/Zip downlaoded? (Fairphone_FP3_8901.2.A.0110.20200109_01092024_user_release-keys.zip)

It is this one ^^

007fred50

@Luksus Nice it works now ! thanks

Luksus

@007fred50 said in Fairphone 3 (FP3):

@Luksus Nice it works now ! thanks

Ahh, thank god :folded_hands:

007fred50

@Luksus shall i upload a file to this? everything

new problem / what is default password to login?
i found the default password (phablet)

007fred50

@Luksus there can i find android 10 to fairphone 3 + ? / zip file

Luksus

@007fred50:
see:

@007fred50 said in Fairphone 3 (FP3):

Can i go back to Farphone OS again? (Android 10)

Yes. "Just" follow this guide: https://support.fairphone.com/hc/en-us/articles/360048050332

if you follow that guide, that I linked above, step by step, you should find the answer:

I will not answer further questions regarding this, sorry, but I am not your personal support.

Janez

Hey,
I tried to flash your build but did not success.
I downloaded your build and run fastboot flash boot halium-boot.img which resulted into fastboot: error: Couldn't parse partition size '0x'.
I have no idea where to start to fix this problem. I tried on newly flashed /e/ 0.12 but with no luck.
All I was able to do was fastboot boot halium-boot.img which for the first time resulted into successful boot but when tried again it got stuck on Fairphone logo.

Building system from scratch does not work for me (I tried commands you described and no luck there) so I am stuck for now.

Luksus

@Janez Hi, the fastboot error Couldn't parse partition size '0x' seems to be a problem of recent fastboot versions.
To go around it you should adjust the command to:

fastboot flash:raw boot bootimage.img

Janez

Thanks a lot Luksus,
now it worked at first try.
I had chance to play with phone for a while so I will try to be useful as much as I can.

SMS working both ways (sending and receiving)
Headphones work, tried 4-pin headphones, microphone not yet
Wi-Fi at home (one router) works well, in work office (several access points) oftenly disconnects

I am also still trying to connect Mullvad VPN via openvpn but did not manage to configure it right yet.

Janez

So I had some time to test the port in real scenario and here are my findings:

SMS works 100% flawlessly including messages from operator and other special numbers
WiFi works as described higher
Did manage to start openvpn through console however phone lost connection completely and went offline. After stopping openvpn everything worked
Phone calls are unreliable.
- Several times I tried and system just did not manage to make call, then it started call normally.
- Some people claimed they tried to call me but nobody answered. But phone did not show any incoming call or missed call. Log of missed calls is completely empty.
Most graphical glitches come when using camera
- Live preview is compressed to upper third of display
- Resolution is fine but noise in pictures is very high

I would really like to try to troubleshoot some of these but I have no clue how to do it so at least I am posting these issues here so someone smarter than me can focus on some of these things.

Luksus

Hi @Janez,
great that it works for you. And thanks for your help.

I can't confirm the telephony and camera bugs as you describe it. For the camera, you could try to change resolution and then switch back again.
Currently I am using another system-build (not GSI).
But I've also had some quirks here and there. Sometimes I could not stop the last phone-call, until I rebooted. Sometimes I was not able to send SMS, they also did not get displayed in history, but after a reboot, the recipient recieved all 3 SMS, I tried to sent.
I think some bugs could also be a result of the dev-build, we are using here.

I must admit that I am also not the one, who knows how to dig deeper into some issues.
I just look around and search for similar issues on similar phones and then try to apply the fix, which someone provided.

As I said above, I am currently testing another system-build, which I am using as daily driver currently. It gets build by the gitlab CI of the ubports repository.
Could you please try if it works for you, when just flash the system.img from here to your FP3?

download
boot to fastboot
then just execute: fastboot flash system system.img
reboot

What you could test here:

does it boot successfully?
does it still boot successfully, if you wipe the data partition (with twrp, or perhaps with fastboot)
- if not, does it boot again if you flash the boot.img from the gitlab CI link above
- if yes, that would be interesting

What I try to figure out here is:

If I understand it correctly, the GSI seems to boot the rootfs (ubports) from the data partition.
The CI build packaged the rootfs into the system-partition.

Normally you would either use boot.img together with system.img from the gitlab CI (option1) or use the halium-boot.img together with the GSI (option2, as you do currently).
The CI build also works, but has less working hardware yet. For example telephony only works when wifi is connected (strange thing).

I am not sure if you know how things work with a/b partitions on that/a phone.
I did flash option1 to the a-partitions and option2 to b-partitions.
Then I could switch with fastboot --set-active=a or fastboot --set-active=b between the options and compere them. The data partion is the same for both.
Then I just flashed the halium-boot.img also to option1 and looked how things work out and somehow it seems to work better than option2.
But what I not tested yet, if it perhaps just boots to the rootfs, which is placed on the data partition by the GSI.
I also would not understand why it would work better than the GSI then, because it would be the same, like booting option2.

Hm, I am not sure if it is clear, what I tried to describe...

007fred50

@Luksus i works for me the last post you added.