It seems those of us who were gratified with a Fairphone and are subscribers of Orange (France) carrier are cursed with a malediction.
I made a post months ago about unremovable Orange bloatware (Orange App Center, Orange Selector, Deezer by Orange, Orange TV, Orange and me…etc) that would reinstall/reenable iself everytime the phone was rebooted as long as you had an Orange SIM card inserted. There’s even an official statement of Fairphone team saying it CAN’T be removed.
But it can. I ended up debloating my phone the radical way with the help of Magisk and its glorious debloated module.
UNFORTUNATELY, this came with a price: for some reason and Orange debloated Fairphone will not propose the OTA updates (it does if I let the Orange garbage apps live.freely on my device, I’ve been able to verify it).
Of course I refuse to surrender. I will not get bullied with carrier crapware.
Therefore I was wondering if there was a way to proceed to a “manual” software update or flashing the latest version of FPOS (without wiping the whole system of course) ?
If what you are trying to accomplish is installing the OTA on a system that has a Magisk patched boot partition, that won’t work.
The updater checks the hashes for all the partitions, so you’ll have to restore the original boot partition before you can install the update. Believe me I have tried a lot of ways… (But there still might be a way I haven’t thought off, I’m still far from an expert )
Why can’t you disable Magisk temporarily and install the update the regular way?
That should keep your modules installed just fine, I believe
For sure, but in my experience this is the first one that I know of that auto-reinstalls bloatware even after a wipe and fresh flash from a constructor OS image.
And I’ve owned 15+ Android devices from the first Samsung Galaxy S times.
I’m gonna continue the conversation here to not spam the other thread.
You can try payload_dumper, that script can create new images by combining factory images and an OTA delta update. I haven’t been able to create trustworthy images with it so far, I wouldn’t try flashing them. They’ll need to match the hashes the system expects…
I’m hoping for payload-dumper-go to get support for it at some point, that one has been much more consistent and stable.
With one of those payload_dumper tools (think it was a fork) I did at least manage to apply the last incremental OTA to the stock full OTA to obtain the raw partitions to extract the vendor blobs for LOS.
Not sure if a flashable OTA could be created from it. FP4 also uses a dynamic partitioning scheme. I had to first “extract” the stock super.img into it’s sub partitions to be able to apply the incremental OTA. Not sure how I would re-assemble that afterwards.
Hope that Fairphone will just update the stock offline installer from time to time.