[HowTo] Update baseband & other firmware
-
All done. Thank you again for your help. I'll report back as soon as I notice anything.
-
@advocatux Thanks, Advocatux. Florian very kindly guided me through my ignorance and it is done now. Appreciate the help.
-
Is there enough feed-back today about benefits of manually flashing (thanks for very clear instructions Florian !) ? Is it worth or better wait for things to be integrated into the upcoming OTA4 (I mean for FP2 phone) ?
-
@livrecinq Hmm not sure we got enough feedback. Seems to make things not worse, and maybe a bit better. Unfortunately the firmware flasher will not be in OTA-4, we found some instabilities and we cannot risk breaking firmware on the devices. So I recommend flash manually if you are confident on your skills
-
@flohack Just a quick question. I always thought that firmware is flashed by OTA and not manually (Android firmware) When the device boot for the first time it creates system.img from the fitmware found on device, right? So, in theory, if I flash Android firmware7.x or 8.x firmware, then wipe it and do a fresh clean install of UT, will the UT(phone) create the system.img from updated firmware (baseband, modem, drivers...)
I'm bit confused here, some clarification would be welcomed. Thanks. -
I always thought that firmware is flashed by OTA and not manually (Android firmware)
@stefano no, UT uses the firmware installed in your device already, that's why is a good idea to update Android to the latest version available for your device before installing UT, so you don't need to update the firmware manually later.
-
@advocatux Even to Android 7 or 8 ? Does UT support Android 7.x and 8.x firmware?
-
@stefano can the supported devices go up to those versions?
-
The Android 7 update for FP2 is scheduled for mid-september.
-
@advocatux So up to 6.x @ the moment, I guess ??
-
@stefano other than FP2, I think so
-
@flohack Many thanks for your advice. So I will try manually asap.
-
@stefano Currently all ports are running on an Android 5.1 base as I remember.
-
@stefano No this is maybe valid for Android but not for UT. When we talk about firmware then its files and drivers written into special partitions that are loaded by kernel drivers during boot. But this is not integrated with the OS at all.
-
Successfully followed your instructions to manually "update baseband and other firmware" on FP2. I have to test now.
-
@advocatux I tried to update the firmware on Pro 5, latest modem on Flyme is CHNOPEN MZ41
So I flashed Flyme 6, then wiped it, installed UT(16.04)
and I've checked the modem version installed now and it says CHNOPEN MZ 024
So it did not update the modem at all? Should I just flash modem.bin file with Fastboot? Or? -
@stefano I dont know what Flyme is doing in the background, but UT does not flash any firmware right now, so no idea. You can flash it manually but I cannot tell you the right partition name. Be very careful with that, you can brick smth probably if you hit the wrong partition.
-
Hi,
After the upgrade from 15.04 to 16.04 (OTA 5 on FP2), great improvement!
With 15.04, I had many reboot with the browser, this was almost unusable.
After around 3 weeks of use with the 16.04, I did not have any reboot when using the morph browser and the battery consumption is far better when mobile data is enabled (it seems similar to consumption with mobile data off).
I do not known if this improvement is due to 16.04 or to the FP2 firmware upgrade (or both).
I am very happy to use the 16.04, Thanks to all the UBports team ! -
@stefano On Pro5, all drivers seems/are stored in the Android Container File System whereas the FP2 and N5 have some dedicated partitions for drivers.
That might explain why an Ubuntu reboot during a call on FP2 do not close the call (modem running on its own or something in that direction!). -
Just want to leave two possibly useful links here:
Firmwarefiles of current FP2 OS release:
https://github.com/WeAreFairphone/modem_zip_generator/releases
Explanation:
https://forum.fairphone.com/t/fp2-modem-firmware/35374But I am not sure, if the firmware did really change from one release to another...
