Thats how it would make sense I guess and is working on the FP4 (most times)
Recently it did not work always for some and I think they could not find the reason, its discussed in this topic
[quote=“hirnsushi, post:340, topic:76839”]
The OTA updates are delta updates and don’t contain a full boot.img, you will have to merge the OTA update(s) with the previous factory images to get a usable boot.img.
[/quote]
Wondering if its the same for FP5 and would it mean using this does not really work?
I’ll try it with just booting next time, but I don’t see it mentioned in install instructions and I’m not sure it would work.
Btw. as asked by @llluuuzzziii - it made sense at the time, as I thougth there wouldn’t be official images available. I might have older kernel, if it was upgraded with OTA, which I suppose (and binwalk on boot.img confirms) is placed on boot partition. But I believe - and please, take in mind that I’m no Android developer, I just know Linux - other parts should be just OK.
And I just realized you probably ment it other way - that there is no sense in doing OTA when you can flash them in recovery. TBH I didn’t know that is possible
As in the end Firephone is releasing factory zips, I’m going to patch boot.img from FP5-TT3L-factory.zip now and I should end up with everything updated.
I hope somebody will arrive too better way than downloading huge factory zip every time, I would really like to have OTA working.
The Fairphone factory image has the “small” boot.img inside as well. Just needs to be extracted or are you saying, that Lineage just posts a separate download link to the boot.img file?
Yeah, I know, that is how I rooted the phone But download from firephone servers is kind of slow and it seems really wastefull to get 2,7GB, unpack it, get small img file, and remove everything else. Network operators are probably happy
Yes, they have separate boot.img, probably for this use case, for every download. You can see it i.e. here: LineageOS Downloads
It would be great, if Firephone would do the same. I’m not sure about best place to ask for this. Maybe @yvmuell knows?
It does seem a bit extra to do that for the company, but one can hope.
Otherwise, there is still this Forum.
And it’s just a zip, so there could be a way to script a download, extract and re-upload to a Forum post every time there is a new factory image available.
They do it for the FP4 I think, so would hope they will do for the FP5 as well moving forward…
Overall my phone isnt rooted so my comments are rather theoretical trying to transfer FP4 knowledge from others more knowledgable to the FP5 as my expectation is, that the FP4 instructions apply to the FP5 the same way.
Unfortunately this would be extremely insecure. SHA sums are inside that huge archive, so nobody would be able to verify that it is original boot.img and nobody tampered with it.
Cool. I’ll write to support to push this a little, but I suppose they are overwhelmed, its still early after FP5 release.
Previous month i doing OTA v106 on rooted without problem (with classic: MagiskApp restore images, Doing OTA without reboot, MagiskApp install to other slot)
But with yesterday 112 update this not work, after reboot, is try load new update from slot B, but after ~15s reboot againd back to A slot with previos 106 system version…
First with Magisk 26.3 as in previous month…
Second i try with latest Magisk 26.4 and result same…
Thirt time i doing this (as still 112 not avaiable for download, but previous 106) :
in Magisk restore images (in actual slot A)
doing OTA update (to other slot B), don’t reboot
in ConnectBot local connection make:
su -
dd if=/dev/block/by-name/boot_b of=/sdcard/boot112stock.dd.img
And with /sdcard/boot112stock.dd.img make as first rooting procedure succesfully
(patch file in MagiskApp, via fastboot boot patched , in MagiskApp direct install)
Just for peace of mind for anyone wanting this, I thought I’d report that the FP5 with the new manual install of Murena/E functions properly when rooted.
It had been my practice until now to use Magisk v23 on all my rooted devices, as it is the last one that natively supported MagiskHide. I can confirm v23 does not work. Magisk v23 will patch the current Murena boot.img, but doesn’t detect root when booted from the patched image. This was unsurprising since Magisk v23 already had problems on the FP3. However, the latest (v26.4 as of right now) Magisk works, and the addon MagiskHide replacement module also works well on the FP5/Murena.
I don’t know if there are any regional differences, but my FP5 is the UK version (and thank heavens Clove ships to Canada!)
Just got the phone last week and got it setup. I’ve seen the update for the past few days and been unable to update. When I try it gets half way through “Downloading and installing” and then just says “Installation failed” with no other error messages.
I have Magisk installed with a few modules (LSPosed, Systemless Hosts, Pixel Xpert, and F-Droid Privileged Extension), and I previously had /e/os installed, followed by a DerpFest GSI, before moving back to stock due to issues.
Has anyone else had issues updating, or is it likely caused by something I have installed? I’m not used to dealing with updates given my last phone went 4 years without one
Assuming you are on pure stock. The update instructions from the OP are still valid. I just followed them like I did with the previous updates. And I also have multiple magisk and lsposed modules installed.
If you want to see the exact error install a logcat reader and filter for update_engine.
Can anyone expand on this? I followed the Magisk guide, which said that I can also flash vbmeta with disabled verification, however I’m getting a checksum mismatch when the OTA is checking vbmeta_b.
I’m not sure what the significance of disabling vbmeta verification is and the language in the Magisk guide is really making it sound like it’s not necessary. (Why even mention it then?)
Since flashing vbmeta wipes data, I’d rather not repeat the effort someone else has put into this before.
