Hello there!
I have been using LineageOS for a couple of months but I am considering switching to IodeOS to be Google-free. To unlock the bootloader, I followed the guide provided by Fairphone. Now, in reading the instructions for installing IodeOS, it is recommended not to unlock critical partitions, but I have already done so. What could be the consequences? Is there a way to restore them to their original state and re-lock them?
Welcome to the community 
You can just relock them. Unlocking the critical partitions doesn’t change them, it only would let you flash them. Un-/locking them does however wipe userdata.
The more important part is to check fastboot flashing get_unlock_ability before you lock your bootloader. If you get a 0 don’t lock it!
4 Likes
Big thanks, that is a relief 
So I got to check with
fastboot flashing get_unlock_ability
In case the return is 1 i relock with
fastboot flashing lock_critical
Then I’m good to go?
Before flashing iodé you might need to consider android securiy patch dates. I think iodé is March but you may be on April with LOS?
1 Like
Hi margana and thanks for the hint i totally forgot about that! I am very lucky tho, I am not upgrading weekly and I am with the release 20230402 wich has March security patches 
3 Likes
ATTEMPT 1
Thought i got the hang of it, never so wrong 
I spent the last couple of hours trying to understand what’s going on with almost 0 results.
I tried following this simple article but i can’t get the recovery flashed. I followed till the 6th point with everything running smoothly but when i try to reboot in iode recovery it is LOS recovery.
Iodé revovery is los. Anyway , you should follow iodé install instructions which are now via fastboot flashing script.
2 Likes
ATTEMPT 2
First of all thanks for your patience 
I tried using the script, it give me an error while starting cause of the SDK version wich i just downloaded from the official site. So digging a bit i found that is a known bug, so i disabled the version checker deleting some row of code in the script. The script then could run successfully but it leaves me with a bootloop. 
Gotta reverse to LOS to use the phone for this week, i will retry surely but i got to study a bit more i guess. Thanks again for your wise help 
Hi there dear Custom ROM flashing pros 
I finally got my second hand FP4 and as planned I directly wanted to install the newest version of iodéOS (4.5) on it.
Unfortuntately the guide of Brotmaa on Brotcast doesn’t exist no longer or isn’t available anymore (https://www.brotcast.ch/blog/2022-11-29-how-to-install-iode-3-on-a-fairphone-4-for-dummies/)
I found an older guide from AlphaElwedritsch but this was from before there was a script for the installation so it seems to not work anymore. (Managed Nextcloud)
Anyways, as @MiKeM did before, I stuck to the official installation procedure on the iodé website (which is very minimalistic) and executed the sh script.
A few commands weren’t working but it somehow installed the recovery anyways (for example the “fastboot format:ext4 cache” didn’t work and the “fastboot flash modem modem.img” also not I think).
But fortunately I didn’t lock the bootloader again!
The phone booted into iodé recovery and wanted to do a factory reset because of some reason which I accepted. since then it is stuck in a bootloop.
I can still access fastboot mode but I honestly have no idea what to do.
I read about some slot a and slot b that I should flash the ROM to but I don’t know how to do this (Locking bootloader after installing Iodé 3.4?).
Anyways, did some of you experience the same issues and could help me out?
That would be awesome!
Many thanks in advance and cheers!
Thats quite old and I would stick to current official instructions and when the script showed errors just do it again.
Hi there @DachschadeCharly! Long story short i’ve got into /e/OS so i can’t really help you for the iode part of the process. If you aim to degoogle and control tracking in your phone I quite recommend /e/OS, can’t compare to any other privacy oriented ROM tho since iode did not work out for me.
The flashing process is very simple since /e/OS come with a dedicated program which do everything for you and in my case it worked flawlessly.
My personal advice to go further into flashing iodeOS is to get confident with fastboot commands and to document further on the flashing process.
Tomorrow I’ll look back into the iode folder sitting in my PC to see if I did go further in the process, I can’t remember right now.
Hoping to come back with some help for you!
Hi @MiKeM
Thanks very much for your reply!
Strange enough after trying the script again like @yvmuell suggested, it suddenly went through and even though apparently a lot of the parts of the script didn’t really work, iodé is running now.
For those who are interested, thats the script running:
iode-4.5-20230926-FP4-fastboot/flash-all.sh
Erasing 'avb_custom_key' OKAY [ 0.012s]
Finished. Total time: 0.018s
Warning: skip copying avb_custom_key image avb footer (avb_custom_key partition size: 0, avb_custom_key image size: 1032).
Sending 'avb_custom_key' (1 KB) OKAY [ 0.005s]
Writing 'avb_custom_key' OKAY [ 0.009s]
Finished. Total time: 0.031s
FAILED (remote: 'GetVar Variable Not found')
fastboot: error: Command failed
Warning: userdata type is f2fs, but ext4 was requested for formatting.
mke2fs 1.46.6 (1-Feb-2023)
Creating filesystem with 58189614 4k blocks and 14548992 inodes
Filesystem UUID: 920d4737-d1f1-42a9-9b01-17bed55d46c5
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done
Writing inode tables: done
Creating journal (262144 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'userdata' (6359 KB) OKAY [ 0.156s]
Writing 'userdata' OKAY [ 0.001s]
Finished. Total time: 0.402s
Sending 'modem_a' (149596 KB) OKAY [ 3.466s]
Writing 'modem_a' OKAY [ 0.371s]
Finished. Total time: 3.920s
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: xxxxxx
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.002s]
Setting current slot to 'a' OKAY [ 0.007s]
extracting boot.img (96 MB) to disk... took 0.211s
archive does not contain 'init_boot.img'
extracting dtbo.img (24 MB) to disk... took 0.036s
archive does not contain 'dt.img'
archive does not contain 'pvmfw.img'
extracting recovery.img (96 MB) to disk... took 0.193s
extracting vbmeta.img (0 MB) to disk... took 0.001s
extracting vbmeta_system.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_vendor.img'
archive does not contain 'vendor_boot.img'
archive does not contain 'vendor_kernel_boot.img'
extracting super_empty.img (0 MB) to disk... took 0.000s
extracting odm.img (1 MB) to disk... took 0.003s
archive does not contain 'boot_other.img'
extracting odm.img (1 MB) to disk... took 0.003s
archive does not contain 'odm_dlkm.img'
extracting product.img (1098 MB) to disk... took 2.856s
extracting system.img (886 MB) to disk... took 2.391s
archive does not contain 'system_dlkm.img'
extracting system_ext.img (386 MB) to disk... took 0.984s
archive does not contain 'system_other.img'
extracting vendor.img (416 MB) to disk... took 1.061s
archive does not contain 'vendor_dlkm.img'
archive does not contain 'vendor_other.img'
extracting boot.img (96 MB) to disk... took 0.188s
archive does not contain 'boot.sig'
Sending 'boot_a' (98304 KB) OKAY [ 2.275s]
Writing 'boot_a' OKAY [ 0.231s]
extracting dtbo.img (24 MB) to disk... took 0.062s
archive does not contain 'dtbo.sig'
Sending 'dtbo' (24576 KB) OKAY [ 0.574s]
Writing 'dtbo' OKAY [ 0.071s]
extracting recovery.img (96 MB) to disk... took 0.210s
archive does not contain 'recovery.sig'
Sending 'recovery' (98304 KB) OKAY [ 2.268s]
Writing 'recovery' OKAY [ 0.220s]
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta' (8 KB) OKAY [ 0.007s]
Writing 'vbmeta' OKAY [ 0.001s]
extracting vbmeta_system.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system' (4 KB) OKAY [ 0.008s]
Writing 'vbmeta_system' OKAY [ 0.001s]
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
Sending 'super' (4 KB) OKAY [ 0.002s]
Updating super partition OKAY [ 1.022s]
Resizing 'odm_a' OKAY [ 0.005s]
Resizing 'product_a' OKAY [ 0.005s]
Resizing 'system_a' OKAY [ 0.005s]
Resizing 'system_ext_a' OKAY [ 0.005s]
Resizing 'system_b' OKAY [ 0.005s]
Resizing 'vendor_a' OKAY [ 0.005s]
Resizing 'vendor_b' OKAY [ 0.005s]
extracting odm.img (1 MB) to disk... took 0.008s
archive does not contain 'odm.sig'
Resizing 'odm_a' OKAY [ 0.006s]
Sending 'odm_a' (1584 KB) OKAY [ 0.039s]
Writing 'odm_a' OKAY [ 0.065s]
extracting product.img (1098 MB) to disk... took 2.977s
archive does not contain 'product.sig'
Resizing 'product_a' OKAY [ 0.005s]
Sending sparse 'product_a' 1/5 (262028 KB) OKAY [ 6.441s]
Writing 'product_a' OKAY [ 0.786s]
Sending sparse 'product_a' 2/5 (262036 KB) OKAY [ 6.413s]
Writing 'product_a' OKAY [ 0.730s]
Sending sparse 'product_a' 3/5 (261676 KB) OKAY [ 6.361s]
Writing 'product_a' OKAY [ 0.806s]
Sending sparse 'product_a' 4/5 (261984 KB) OKAY [ 6.389s]
Writing 'product_a' OKAY [ 0.790s]
Sending sparse 'product_a' 5/5 (73064 KB) OKAY [ 1.810s]
Writing 'product_a' OKAY [ 0.285s]
extracting system.img (886 MB) to disk... took 2.398s
archive does not contain 'system.sig'
Resizing 'system_a' OKAY [ 0.005s]
Sending sparse 'system_a' 1/4 (262084 KB) OKAY [ 6.381s]
Writing 'system_a' OKAY [ 0.853s]
Sending sparse 'system_a' 2/4 (262108 KB) OKAY [ 6.391s]
Writing 'system_a' OKAY [ 0.732s]
Sending sparse 'system_a' 3/4 (262004 KB) OKAY [ 6.398s]
Writing 'system_a' OKAY [ 0.784s]
Sending sparse 'system_a' 4/4 (118012 KB) OKAY [ 2.890s]
Writing 'system_a' OKAY [ 0.369s]
extracting system_ext.img (386 MB) to disk... took 1.047s
archive does not contain 'system_ext.sig'
Resizing 'system_ext_a' OKAY [ 0.005s]
Sending sparse 'system_ext_a' 1/2 (256199 KB) OKAY [ 6.439s]
Writing 'system_ext_a' OKAY [ 1.931s]
Sending sparse 'system_ext_a' 2/2 (131636 KB) OKAY [ 3.230s]
Writing 'system_ext_a' OKAY [ 0.481s]
extracting vendor.img (416 MB) to disk... took 1.098s
archive does not contain 'vendor.sig'
Resizing 'vendor_a' OKAY [ 0.005s]
Sending sparse 'vendor_a' 1/2 (262140 KB) OKAY [ 6.315s]
Writing 'vendor_a' OKAY [ 0.768s]
Sending sparse 'vendor_a' 2/2 (164528 KB) OKAY [ 4.063s]
Writing 'vendor_a' OKAY [ 0.467s]
Finished. Total time: 124.218s
Sending 'abl_a' (148 KB) OKAY [ 0.004s]
Writing 'abl_a' OKAY [ 0.004s]
Finished. Total time: 0.022s
Sending 'aop_a' (174 KB) OKAY [ 0.005s]
Writing 'aop_a' OKAY [ 0.005s]
Finished. Total time: 0.020s
Sending 'bluetooth_a' (940 KB) OKAY [ 0.023s]
Writing 'bluetooth_a' OKAY [ 0.010s]
Finished. Total time: 0.044s
Sending 'core_nhlos_a' (111884 KB) OKAY [ 2.692s]
Writing 'core_nhlos_a' OKAY [ 0.314s]
Finished. Total time: 3.062s
Sending 'devcfg_a' (42 KB) OKAY [ 0.002s]
Writing 'devcfg_a' OKAY [ 0.005s]
Finished. Total time: 0.017s
Sending 'dsp_a' (65536 KB) OKAY [ 1.681s]
Writing 'dsp_a' OKAY [ 0.192s]
Finished. Total time: 1.881s
Sending 'featenabler_a' (84 KB) OKAY [ 0.003s]
Writing 'featenabler_a' OKAY [ 0.005s]
Finished. Total time: 0.018s
Sending 'hyp_a' (399 KB) OKAY [ 0.010s]
Writing 'hyp_a' OKAY [ 0.008s]
Finished. Total time: 0.028s
Sending 'imagefv_a' (524 KB) OKAY [ 0.015s]
Writing 'imagefv_a' OKAY [ 0.005s]
Finished. Total time: 0.029s
Sending 'keymaster_a' (257 KB) OKAY [ 0.007s]
Writing 'keymaster_a' OKAY [ 0.006s]
Finished. Total time: 0.023s
Sending 'multiimgoem_a' (13 KB) OKAY [ 0.001s]
Writing 'multiimgoem_a' OKAY [ 0.004s]
Finished. Total time: 0.014s
Sending 'qupfw_a' (53 KB) OKAY [ 0.002s]
Writing 'qupfw_a' OKAY [ 0.005s]
Finished. Total time: 0.015s
Sending 'tz_a' (2944 KB) OKAY [ 0.071s]
Writing 'tz_a' OKAY [ 0.018s]
Finished. Total time: 0.101s
Sending 'uefisecapp_a' (121 KB) OKAY [ 0.004s]
Writing 'uefisecapp_a' OKAY [ 0.005s]
Finished. Total time: 0.018s
Sending 'xbl_config_a' (94 KB) OKAY [ 0.003s]
Writing 'xbl_config_a' OKAY [ 0.006s]
Finished. Total time: 0.019s
Sending 'xbl_a' (3298 KB) OKAY [ 0.080s]
Writing 'xbl_a' OKAY [ 0.021s]
Finished. Total time: 0.113s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.000s
Next I try to root it 
Thanks and cheers!
DC
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.