[HowTo] [FP2] Update baseband & other firmware
advocatux last edited by
@stefano other than FP2, I think so
livrecinq last edited by
@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.
livrecinq last edited by
Successfully followed your instructions to manually "update baseband and other firmware" on FP2. I have to test now.
Stefano last edited by
@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.
ublublu last edited by
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 !
tera last edited by tera
@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!).
Luksus last edited by
Just want to leave two possibly useful links here:
Firmwarefiles of current FP2 OS release:
But I am not sure, if the firmware did really change from one release to another...
Ingo last edited by
The most recent real change was included in the April 2018 update.
One of the next updates will likely include a change to fix a bug about not being able to turn the phone on while charging.
tommiedom last edited by
@flohack nice work! I got the OTA-7 update now. Again a more stable and faster FP2!
Is a firmware update included in this and/or previous OTA updates, or is it still worth it to flash new firmware manually and follow this howto?
@tommiedom No, I think the firmware update was still held back due to concerns about stability. We cannot risk flashing devices to their digital death
tommiedom last edited by tommiedom
 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.