[HowTo] Update baseband & other firmware

tommiedom

@flohack thnks
[edit] Update worked flawlessly. I had to change usb-port, because fastboot gave a message: waiting for any device... Changing usb-port worked.

My experience so far: no significant improvement. phone still reboots

if typing a text takes a while (half an hour) in browser, signal, sms, etc.
after a while if to many apps are used simultaneously.
Also, sometimes (a couple of times in a month) I find my phone rebooted in the morning.

Don't know if this is FP2-behaviour.

Now, I used the update package as given by @flohack. @Ingo said above that "The most recent real change was included in the April 2018 update." So I expect no improvement from using another more current update package.

RedXXIII

I flashed my FP2 from Android to UT in January 2019. Do I still need to do this manual firmware update?

flohack

@RedXXIII Well if you had a recent Android version with all updates then probably not.

Fla

There is a new firmware at https://github.com/WeAreFairphone/modem_zip_generator/releases since February 2020, did anyone flash it? How did it go?

A Former User

@fla I did it. It works well ! In fact I flashed the entire FP Open OS image before installing Ubuntu Touch, because with Lineage OS making calls was becoming trickier and trickier and I suspect the gap between the firmware and the image is the culprit.

But yes, it works well : I can call reliably, the battery life is longer (but I'm not a heavy user, so does it really count ?), and random reboots are really rare (like, once in six months or so). By the way do you have any news on Android 9 for FP2 ?

Fla

@luna are the instructions in the first post still up-to-date?

Ingo

The download URL in the first post is definitely outdated.

Edit: taking the archive from https://github.com/WeAreFairphone/modem_zip_generator/releases/tag/19.11.2 contains the corresponding images. The naming is slightly different as the image files are called like the partion they're supposed to be flashed to.

A Former User

@fla yes they are. But as previously said, I don't know how those firware images are linked with the Android kernel. You can flash them with the kernel you currently have, but maybe they won't work as reliably as with the kernel in the zip folder... that is what I tend to think. I hope that I'm wrong and it's just my FP2's top module that shows its age, but maybe you're safer with the full image and a clean reinstall of UT.

That implies a backup of your data - a backup of /home/phablet is sufficient for me.

Emphrath

@luna great ! i'll do that as soon as I can. Thanks for the update

A Former User

@emphrath you're welcome

flohack

If someone of you would write me a text to replace my initial post with the new instructions feel free ^^

flohack

Hi, I have moveds that article to the FP2 subforum now, pinned it and updated the link: Now it points to 2 optins, either use the 7.1 or the 9.0 firmware, I maybe recommend to start with 7.1 - Can anyone tell me if the downloads maybe contain the same images, so we can point only to one?

As of today there will be no more firmware releases for the FP2, so its safe to assume that will be the last update of this article

tommiedom

Where can i find the current firmware? Cos i already did an update in the past..

s3r0

@tommiedom
https://github.com/WeAreFairphone/modem_zip_generator/releases
19.11.2 released on Feb 11, 2020

@Flohack

6.5. sudo fastboot flash dbi sdi.mbn

ls fp2-gms-19.11.2-manual-v2/images
boot.img           MD5SUMS       recovery.img  sbl1.mbn    splash.img  tz.mbn
emmc_appsboot.mbn  NON-HLOS.bin  rpm.mbn       SHA256SUMS  system.img

There is no sdi.mbn file.
Can I flash it anyway?

flohack

@s3r0 No idea better not flash anything thats not 100% safe

tommiedom

@s3r0 i meant, the current firmware of my phone

s3r0

@tommiedom
Good question

I have this power-on bug too, but flashing seems to be a bit risky..
Has anyone flashed the latest (19.11.2) firmware release?

Emphrath

@s3r0 yes. By flashing the entire fairphone OS, so you don't have to worry about which part of the firmware goes where.