FP4: Iode 7 status / Issue Tracker?

Hi all!

In the view of wiping my data, I wonder if backing up with SeedVault (solution included in Iodé) does the full trick, or else there is something else I have to do.

I have never done a backup before. Anyone who can give some light about it?

Thank you!

Hi all,
updating an FP4 from iodé 6.13 to 7.t following these instructions didn’t work. After installing the package prep of the local update, the UI becomes disabled, restart doesn’t appear.
Restarting manually asks for the data reset and the phone starts up 6.13 again. I also tried the 2nd method, same result.
Then I updated to 6.14 and tried it again.
This time the updater doesn’t do anything.

Then I tried to install 7.4 from scratch following the instructions here:
https://gitlab.iode.tech/ota/ota#fp4-fp5-fp6
but after downloading iode-7.4-20260403-FP4-fastboot.zip and iode-7.4-20260403-FP4-fastboot.zip.sha256 I realized that both files are just approx. 32 kB and
sha256sum -c iode-7.4-20260403-FP4-fastboot.zip.sha256 complains not having a correct checksum. Also the file iode-7.4-20260403-FP4-fastboot.zip cannot be unzipped.
To me it seems that the files are corrupt. Can anyone please check?

:smiley: Understanding how to download files from gitlab helps:

  • Right-click to the link in the browser and save target doesn’t download the correct file.
  • Clicking the the link and then clicking Download… downloads the correct file.

Installing iodéOS 74. from scratch finally worked.

Now installing all apps again… :smiley:

1 Like

Run the seedvault backup. It will show you afterwards which apps have been saved. There are some apps that will not allow saving (for example Threema). You will have to save them seperately (backup feature in-app). Also copy “files” like documents etc. to your computer or an usb stick seperately (when I moved from CalyxOS to iodéOS, those files had not been transferred/included in the seedvault backup; don’t know if the error was on my side, but better be safe than sorry: connect to your computer via usb and copy those files there.)

No risk, no fun :wink:

PS: Change settings of seedvault to save the apk-files of your apps themselves, too.

1 Like

FP4 owner / Iodé 6.14 user speaking…

There is a lot in this thread that I do not understand.

1/ If it is stated that a locked bootloader is a problem, why isn’t the instruction given of how to unlock the bootloader?

2/ upon inspection I find in the Developer options: Allow the bootloader to be unlocked. Does that allowance unlock the bootloader? Or what else should be done to unlock it?

3/ I do not understand whether or how unlocking the bootloader prevents a complete reinstall of the phone with all apps and data. I would like to see more info on this matter. Or is the bootlocker thing only needed to prevent bricking?

Please provide explanations and assistance.

Greetz

Roland

Basically all your questions can be answered by this response: Upgrading from v6 to v7 with a locked bootloader will require a “factory reset”. It is not solved by unlocking the bootloader, as that will also wipe your user data, the same as a “factory reset”.

So, you do not need to unlock the bootloader, it can remain locked, but again, you need to “factory reset” when prompted (you are only prompted if it detects your bootloader is locked). This whole issue is due to a bug with the Fairphone firmware that our lead developer has not been able to solve even with several rounds of trial and error and patch applying, etc. with updates from Fairphone over the past 3+ months.

1 Like

In addition to @MissPiggy 's excellent advice, here are my notes on Seedvault usage:

Seedvault is built in (Settings > System > Backup), it does really well for backup and restore but there are some apps it doesn’t restore the settings and data for (the apps themselves will be reinstalled). Here is a non-definitive list that I have for apps I use that aren’t able to have their settings and data restored by Seedvault:

DAVx5
Thunderbird
Element
Signal
Firefox / iode browser
AntennaPod
Tailscale

You will note a common theme that they are apps that require OAuth / 2FA login and/or are encrypted. It makes sense these would not be able to be restored as it could be considered a security concern.

But (nearly) all of those also sync to online services, or have backup and restore options from within the apps themselves.

Still, I will admit it is not as easy for you if it is your first time to backup and restore, especially if to the same device. I practiced this several times with 2 devices so I could go to the original device to get what wasn’t part of seedvault after I found it didn’t get something. Sorry it isn’t easier.

1 Like

Hi Rik, pls be not surprised that I do not know that unlocking a bootloader automatically results in a factory reset

1 Like

Option 1, “ then reset you data”

What does that mean, and how to?

In my limited experience “to reset” means to return everything to “original”. In the case of a data carrier, therefore, to wipe it empty.

So, please try to understand my confusion here. I shall seriously appreciate more guidance in this matter.

followed all instructions on the messaging app.

Download the ZIP file for version 7 from the News app.

Use the update app to open the file as a local update.

But nothing happened more than 1 hour. Shows only one following message “The update package willbe installed.”

But there are no installation

FP4
Unlocked (never locked since iodeos)
Last update 6.14

I am a bit thrown off by this. So, updating following the updater instructions does not work? Is this the case for other people too?

I do not feel very confident on updating manually (github download , etc .). But if I finally do it, will I afterwards get a system that self-updates via the updater, as usual?

Unfortunately I had this issue on my FP4, yes. It seems that @noone had exactly the same.

@Roland But flashing from scratch means you lose all data and you need to re-install all apps and re-configure everything. Don’t forget to backup before. :wink:

After the update failed, I followed the instruction below for flashing 7.4. I wrote it 3 years ago for an older version, but it is still applicable.

I am running iodéOS on multiple phones since 3 years and regularly updated to new versions. I never had any issue until the update to iodéOS 7.x. Hence I’m confident that updating to newer 7.x versions will be self-updating.

@andi Was your bootloader looked or unlooked?

I think it was unlocked, but not 100% sure.

Actually, it would be very helpful, for starters, if Iodé gave less ambiguous instructions.

For example, to write “restore your data by doing [this or that]”, rather than to “reset your data”. The more so, since users are requesting such explanations.

So far, I gather that they do indeed mean to instruct to “restore”. The means: probably SeedVault combined with additional backups. As an additional I would suggest to use MyPhoneExplorer. I am waiting for confirmation before I try.

Just updated with the v6v7 updater.apk

Everything went smooth. My bootloader is open so there was no prompt to factory reset my phone.

No restore needed. Everything is as it should be.

THX

I’ve performed the update now, however the instructions given in the updater app don’t work with a locked bootloader. After being prompted to factory reset the device, it rolled back the update and rebooted to iode v6/android 15.

So instead I unlocked the bootloader, performed the update, and locked it again. It’s working now.

Thanks for your work.

Can you shortly described your steps? I have the same problem (FP4 falls back to Android 15).

  • Enable OEM unlocking and USB debugging in developer options
  • Connect to a computer
  • adb reboot bootloader
  • Wait until it reboots
  • fastboot flashing unlock
  • reboot (skip through most setup options, but connect to the internet and set up a screen lock)
  • install update
  • reboot from the intaller
  • enable USB debugging in developer options again
  • adb reboot bootloader
  • wait until it reboots
  • fastboot flashing lock
  • reboot (Set up device properly on first boot)
  • disable OEM unlocking in developer options
  • reboot
3 Likes